Production servers num_sql_socks
I've read a few posts about increasing this value when " There are no DB handles to use" occur. Not sure if it's a good idea. Granted your DB is fast enough to query quickly. Upping this value on a slow DB will severely degrade performance. What's sort of values are you guys using for production servers? -- Regards Stelio Gouveia -- Skyrove Software Engineer, Skyrove (Pty) Ltd Technology Top 100 Award Winner (2006) Mobile: +27 82 34 09 120 Tel: +27 861 ROVERS (0861 768 377) Fax: +27 86 6204077 Email & Gtalk: stelio@skyrove.com Skype: skyrove_sa Web: www.skyrove.com This message contains confidential information. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message.
We set num_sql_socks to 25. We had them set to 10 but ran into issues when massive numbers of subscribers were attempting to enter the network at once - for example when we would power cycle a base station with 400 subscribers on it for maintenance. Ben Wiechman From: freeradius-users-bounces+ben=wisper-wireless.com@lists.freeradius.org [mailto:freeradius-users-bounces+ben=wisper-wireless.com@lists.freeradius.or g] On Behalf Of Stelio Gouveia Sent: Thursday, March 05, 2009 8:55 AM To: freeradius-users@lists.freeradius.org Subject: Production servers num_sql_socks I've read a few posts about increasing this value when " There are no DB handles to use" occur. Not sure if it's a good idea. Granted your DB is fast enough to query quickly. Upping this value on a slow DB will severely degrade performance. What's sort of values are you guys using for production servers? -- Regards Stelio Gouveia -- Skyrove Software Engineer, Skyrove (Pty) Ltd Technology Top 100 Award Winner (2006) Mobile: +27 82 34 09 120 Tel: +27 861 ROVERS (0861 768 377) Fax: +27 86 6204077 Email & Gtalk: stelio@skyrove.com Skype: skyrove_sa Web: www.skyrove.com This message contains confidential information. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message.
Hi,
Granted your DB is fast enough to query quickly. Upping this value on a slow DB will severely degrade performance.
What's sort of values are you guys using for production servers?
we found that any value over 20 caused issues with mysql... we moved to postgresql anyway a year back. alan
If it is not a secret, how many users do you have (active users in the same time) and how many connections per minute can your system handle without problems. A.L.M.Buxey@lboro.ac.uk wrote:
Hi,
Granted your DB is fast enough to query quickly. Upping this value on a slow DB will severely degrade performance.
What's sort of values are you guys using for production servers?
we found that any value over 20 caused issues with mysql... we moved to postgresql anyway a year back.
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Thu, Mar 05, 2009 at 09:19:19AM -0600, Ben Wiechman wrote:
We set num_sql_socks to 25. We had them set to 10 but ran into issues when massive numbers of subscribers were attempting to enter the network at once - for example when we would power cycle a base station with 400 subscribers on it for maintenance.
Ben Wiechman
From: freeradius-users-bounces+ben=wisper-wireless.com@lists.freeradius.org [mailto:freeradius-users-bounces+ben=wisper-wireless.com@lists.freeradius.or g] On Behalf Of Stelio Gouveia Sent: Thursday, March 05, 2009 8:55 AM To: freeradius-users@lists.freeradius.org Subject: Production servers num_sql_socks
I've read a few posts about increasing this value when " There are no DB handles to use" occur. Not sure if it's a good idea.
Granted your DB is fast enough to query quickly. Upping this value on a slow DB will severely degrade performance.
What's sort of values are you guys using for production servers?
-- Regards Stelio Gouveia
The value depends on three inter-dependent factors: 1. the time to answer a query by your DB backend 2. how many queries can be handled reasonably by your backend 3. your request rate Typically, there is a sweet spot, performance-wise for this setting. If your backends are not available when needed, you will have people unable to connect. If you increase the number above which your backend DB can safely handle, you will have a total service outage in a high load situation. A load test with your setup is the best option. Good luck. Cheers, Ken
participants (5)
-
A.L.M.Buxey＠lboro.ac.uk -
Ben Wiechman -
Kenneth Marshall -
Marinko Tarlac -
Stelio Gouveia