freeradius, memory consumption
Hi, I am using Freeradius for authorization with mysql. In my sql I have about 15k user entries and there si about 50 active calls all the time (just for information about traffic). Now Freeradius is in production for abot 4 months and I did not noticed any problems (works perfect). Today I noticed that it is using around 77% of memory. Is this normal? Thanks! Miha root 27533 0.0 77.4 13524108 9500600 ? Ssl Mar26 29:51 radiusd
You're using FR just for authorization and not for accounting and session control ? On 3.9.2012 10:16, Miha wrote:
Hi,
I am using Freeradius for authorization with mysql. In my sql I have about 15k user entries and there si about 50 active calls all the time (just for information about traffic).
Now Freeradius is in production for abot 4 months and I did not noticed any problems (works perfect). Today I noticed that it is using around 77% of memory. Is this normal?
Thanks!
Miha
root 27533 0.0 77.4 13524108 9500600 ? Ssl Mar26 29:51 radiusd - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Mon, Sep 3, 2012 at 3:16 PM, Miha <miha@softnet.si> wrote:
Hi,
I am using Freeradius for authorization with mysql. In my sql I have about 15k user entries and there si about 50 active calls all the time (just for information about traffic).
Now Freeradius is in production for abot 4 months and I did not noticed any problems (works perfect). Today I noticed that it is using around 77% of memory. Is this normal?
AFAIK no. What version are you using? IIRC there were memory leak issues on some old version. Just in case it's a known issue. 2.1.12 or distro-maintained-2.1.10 should be good. -- Fajar
Miha wrote:
Now Freeradius is in production for abot 4 months and I did not noticed any problems (works perfect). Today I noticed that it is using around 77% of memory. Is this normal?
No. There may be issues with older versions, though. After much delay, version 2.2.0 will be released on September 10. Upgrade to that, and all known issues will be fixed. Alan DeKok.
On Mon, Sep 03, 2012 at 10:41:31AM +0200, Alan DeKok wrote:
After much delay, version 2.2.0 will be released on September 10.
...falls off chair. What year? ;-) Matthew -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Architect (UNIX and Networks), Network Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>
Matthew Newton wrote:
On Mon, Sep 03, 2012 at 10:41:31AM +0200, Alan DeKok wrote:
After much delay, version 2.2.0 will be released on September 10.
...falls off chair.
What year?
2012.
;-)
I know... There have been a number of surprising developments in the past year. Sorry for the delay. Once 2.2.0 is released, I think we should move to a fixed release cycle, every 3 months. I'll also try to finish off some final work for 3.0, too. Alan DeKok.
On 09/04/2012 03:43 AM, Alan DeKok wrote:
Once 2.2.0 is released, I think we should move to a fixed release cycle, every 3 months. I'll also try to finish off some final work for 3.0, too.
Just so you know, a 3 month release cycle means most enterprise distributions will be significantly behind the FreeRADIUS's current version. This is even twice as fast as the distribution with the shortest release cycle, Fedora which is 6 months. Thus when the advice offered from the list is "upgrade to the current release" there will be a significant number of users who will find this difficult or impossible advice to heed due to a variety of structural issues, internal policy concerns or the technical ability to deploy from from source. Even if those technical skills exist there are many organizations which prohibit deploying locally built software, especially mission critical system services such as authentication. I understand the appeal of "release early, release often" and in some contexts that is optimal but I don't believe that applies to critical infrastructure system daemons, they by their very nature are in a different class, one that benefits from longer release cycles with a greater focus on stability. John -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
John Dennis wrote:
Just so you know, a 3 month release cycle means most enterprise distributions will be significantly behind the FreeRADIUS's current version. This is even twice as fast as the distribution with the shortest release cycle, Fedora which is 6 months.
OK.
I understand the appeal of "release early, release often" and in some contexts that is optimal but I don't believe that applies to critical infrastructure system daemons, they by their very nature are in a different class, one that benefits from longer release cycles with a greater focus on stability.
A 6 month release cycle is fine by me. Alan DeKok.
participants (6)
-
Alan DeKok -
Fajar A. Nugraha -
John Dennis -
Marinko Tarlać -
Matthew Newton -
Miha