Hello, all. It's a question to all members of freeradius community :) I'm going to use freeradius in my billing system. That's why i'd like to know, what is the maximum loading on the freeradius-server (average number of online users during the day, total number of users, interval of alive packets etc.). Maybe there is some tests of freeradius's perfornance or maybe someone is using freeradius in his billing system... It would be very interesting for all members of community. Thanks beforehand.
M K wrote:
It's a question to all members of freeradius community :) I'm going to use freeradius in my billing system. That's why i'd like to know, what is the maximum loading on the freeradius-server (average number of online users during the day, total number of users, interval of alive packets etc.). Maybe there is some tests of freeradius's perfornance or maybe someone is using freeradius in his billing system... It would be very interesting for all members of community.
See the main page of freeradius.org, and click on the "fast" link. http://freeradius.org/features/fast.html In short, your performance is limited by the DB. Not by FreeRADIUS. Make sure your DB is fast. Alan DeKok.
It's a question to all members of freeradius community :) I'm going to use freeradius in my billing system. That's why i'd like to know, what is the maximum loading on the freeradius-server (average number of online users during the day, total number of users, interval of alive packets etc.).
Freeradius can handle tens of thousands of requests per second. Your billing sistem most likely can't handle much more than 100 per second. Don't worry about freeradius - it will easily outperform your billing sistem. You might need to slow it down so it doesn't crash the billing. I use buffered-sql virtual server to make accounting off-line. My billing application has to connect to 4 databases (radius, user details, account status and account history) so it was quite costly running it in real time at peak times. Ivan Kalik Kalik Informatika ISP
On Mon, Mar 16, 2009 at 10:21 PM, <tnt@kalik.net> wrote:
I use buffered-sql virtual server to make accounting off-line. My billing application has to connect to 4 databases (radius, user details, account status and account history) so it was quite costly running it in real time at peak times.
Are you using interim updates? If yes, is there any special method to make it more efficient? On a DSL environment where users are mostly auto-connect (i.e. modem redials automatically when disconnected) interim updates seems to contribute most load. Regards, Fajar
Are you using interim updates?
No. This is ordinary dial-up.
If yes, is there any special method to make it more efficient? On a DSL environment where users are mostly auto-connect (i.e. modem redials automatically when disconnected) interim updates seems to contribute most load.
Do all updates come at the same time? Using buffered-sql or such virtual servers is designed for that. default will reply to the NAS instantly and then pass on the requst to buffered-sql to process the requests at it's own pace. That will even the load. Ivan Kalik Kalik Informatika ISP
On Tue, Mar 17, 2009 at 5:39 PM, <tnt@kalik.net> wrote:
On a DSL environment where users are mostly auto-connect (i.e. modem redials automatically when disconnected) interim updates seems to contribute most load.
Do all updates come at the same time? Using buffered-sql or such virtual servers is designed for that. default will reply to the NAS instantly and then pass on the requst to buffered-sql to process the requests at it's own pace. That will even the load.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
How does buffered-sql read the detail file? I see filename = ${radacctdir}/detail but it does not show (for example) what happens when freeradius is stopped and restarted before all entries in the detail file processed : Does it re-process everything, or does it ignore everything and only process "new" detail log. Regards, Fajar
Hi,
but it does not show (for example) what happens when freeradius is stopped and restarted before all entries in the detail file processed : Does it re-process everything, or does it ignore everything and only process "new" detail log.
if you run it, you'll see what it does and how it does it. data is appended until the detail module has dealt with it - ie nothing lost from detail file when stopping/starting the server alan
How does buffered-sql read the detail file? I see
filename = ${radacctdir}/detail
but it does not show (for example) what happens when freeradius is stopped and restarted before all entries in the detail file processed : Does it re-process everything, or does it ignore everything and only process "new" detail log.
It renames detail to detail.work and processes that file while the server writes new requests to detail. When it's done processing detail.work it renames detail again etc. Restarting the server doesn't wipe out detail or detail.work. Ivan Kalik Kalik Informatika ISP
Sorry for bothering but what if detail file is on daily basis ... detail-20090101 for example... On Tue, Mar 17, 2009 at 12:43 PM, <tnt@kalik.net> wrote:
How does buffered-sql read the detail file? I see
filename = ${radacctdir}/detail
but it does not show (for example) what happens when freeradius is stopped and restarted before all entries in the detail file processed : Does it re-process everything, or does it ignore everything and only process "new" detail log.
It renames detail to detail.work and processes that file while the server writes new requests to detail. When it's done processing detail.work it renames detail again etc. Restarting the server doesn't wipe out detail or detail.work.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Sorry for bothering but what if detail file is on daily basis ... detail-20090101 for example...
If you want to keep daily detail file then create two detail instances - one that is rotated daily and one that writes to a file with constant name. Point detail reader to one with the constant name. That file is deleted as buffered-sql processes it so there will be no record in files as records are inserted in sql. Ivan Kalik Kalik Informatika ISP
Hi,
Sorry for bothering but what if detail file is on daily basis ... detail-20090101 for example...
As Ivan says - if you are using buffered-sql and tking in that detail file, then there will be nothing to rotate or deal with - everything that is currently in the detail file get slurped into the SQL alan
participants (6)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Fajar A. Nugraha -
M K -
Marinko Tarlac -
tnt＠kalik.net