@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
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
-bounces+ben=wisper-wireless@lists.freeradius.org
[mailto:freeradius-users-bounces+ben=wisper-wireless@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
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.
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.bu...@lboro.ac.uk wrote:
Hi,
Granted your DB is fast enough to query quickly.
Upping this value on a slow DB will severely
Hi,
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.
around 15k concurrent users, hundreds of thousand per minute could be handled
(when we last did a load test)
alan
-
List
6 matches
Mail list logo