Hello, we are using Freeradius 3:0.18 and we see that when we activate accounting logs the load average of the freeradius machine is very height ( 197%) however when we desactivate these logs the load average is less than 10%, our server has 8VCPU and we receive 3000 accounting start / second, is there any solution to reduce cpu consumption when activating detail module ? Thanks Bassem
1. If possible, upgrade to the latest 3.0.19 2. if the account packets are keeping in the filesystem, please check the IOPS. On Thu, Apr 25, 2019 at 12:50 PM Bassem Mettichi <mettichi@gmail.com> wrote:
Hello,
we are using Freeradius 3:0.18 and we see that when we activate accounting logs the load average of the freeradius machine is very height ( 197%) however when we desactivate these logs the load average is less than 10%, our server has 8VCPU and we receive 3000 accounting start / second, is there any solution to reduce cpu consumption when activating detail module ?
Thanks Bassem - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 25/04/2019 16:46, Bassem Mettichi wrote:
Hello,
we are using Freeradius 3:0.18 and we see that when we activate accounting logs the load average of the freeradius machine is very height ( 197%) however when we desactivate these logs the load average is less than 10%, our server has 8VCPU and we receive 3000 accounting start / second, is there any solution to reduce cpu consumption when activating detail module ?
AIUI the average single core load is the load average divided by the number of cores. In your case that comes to ~25%. Is a system running at a quarter of capacity a problem? I use the i7z utility to monitor how the CPU is behaving. This may be informative. https://delightlylinux.wordpress.com/2016/12/20/i7z-what-is-your-i7i5i3-cpu-... https://superuser.com/questions/729634/load-average-and-processor-count
Hello, the problem is that when the load average exceeds the value of 50% we received more conflicting packets on radiusLog file and our freeradius server starts dropping packets that is why iam asking you about this however when we disable detail module we don't receive conflicting packets. Thanks Bassem Le jeu. 25 avr. 2019 à 17:29, Dom Latter <freeradius-users@latter.org> a écrit :
On 25/04/2019 16:46, Bassem Mettichi wrote:
Hello,
we are using Freeradius 3:0.18 and we see that when we activate accounting logs the load average of the freeradius machine is very height ( 197%) however when we desactivate these logs the load average is less than 10%, our server has 8VCPU and we receive 3000 accounting start / second, is there any solution to reduce cpu consumption when activating detail module ?
AIUI the average single core load is the load average divided by the number of cores. In your case that comes to ~25%.
Is a system running at a quarter of capacity a problem?
I use the i7z utility to monitor how the CPU is behaving. This may be informative.
https://delightlylinux.wordpress.com/2016/12/20/i7z-what-is-your-i7i5i3-cpu-...
https://superuser.com/questions/729634/load-average-and-processor-count - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Apr 25, 2019, at 12:54 PM, Bassem Mettichi <mettichi@gmail.com> wrote:
the problem is that when the load average exceeds the value of 50% we received more conflicting packets on radiusLog file and our freeradius server starts dropping packets that is why iam asking you about this however when we disable detail module we don't receive conflicting packets.
You have likely set up the detail file with "locking = yes". Change that, and it should help. If you don't have "locking = yes", then the problem is just load. The detail file writer isn't optimized for performance. It just writes lines to a file. This is a common problem with high load systems. You can't just take a stock config and expect it to do everything you want at 3K-10K packets/s. You have to understand what it's doing, what you need it to do, and configure it accordingly. Alan DeKok.
participants (4)
-
Alan DeKok -
Bassem Mettichi -
Dom Latter -
Jorge Pereira