SQLIPPool performance issue

[Roy Walker]

I upgraded to 8.2.4 and the performance does not seem to be any
different.  I guess my next step is to try looking at the query log and
see which is the worst.

-----Original Message-----
From:
freeradius-users-bounces+rwalker=sensorlogic.com at lists.freeradius.org
[mailto:freeradius-users-bounces+rwalker=sensorlogic.com at lists.freeradiu
s.org] On Behalf Of Kenneth Marshall
Sent: Wednesday, July 25, 2007 1:30 PM
To: FreeRadius users mailing list
Subject: Re: SQLIPPool performance issue

Mr. Walker,

It sounds as if you need to tune your postgresql installation.
By the way, postgresql 8.2.4 will out perform 8.1.9. You should
probably turn on query logging and see what the queries are and
if they can be optimized. Maybe you are missing an index or two,
although you may just have too little I/O capacity. Good luck.

Ken

On Wed, Jul 25, 2007 at 01:19:04PM -0500, Roy Walker wrote:
> I am having a problem with the SQLIPPOOL performance.  This is
migration
> of an existing radius server using flat user files (old server is
> running radius 1.1.0).
> 
>  
> 
> Running freeradius-server-snapshot-20070705 on a P4 2.8GHZ machine
> 
> Database is Postgres 8.1.9 running on a monstrous Sun Opteron machine.
> 
>  
> 
> When radius starts taking requests (it's  a lot of requests, about
> 500/sec), the load on the radius server spikes to 100 and it
eventually
> stops taking requests completely.  The database is never above 0.05
> load.
> 
>  
> 
> I see messages like these in the radius logs:
> 
> Wed Jul 25 10:29:15 2007 : Info: IP Allocation FAILED from
general_pool
> (did slogic.t-mobile.com cli 14696841693 port 0 user 14696841693)
> 
> Wed Jul 25 10:29:15 2007 : Info: IP Allocation FAILED from
general_pool
> (did slogic.t-mobile.com cli 19723023688 port 0 user 19723023688)
> 
> Wed Jul 25 10:29:15 2007 : Info: IP Allocation FAILED from
general_pool
> (did slogic.t-mobile.com cli 14696845996 port 0 user 14696845996)
> 
> Wed Jul 25 10:29:15 2007 : Info: IP Allocation FAILED from
general_pool
> (did slogic.t-mobile.com cli 14696846177 port 0 user 14696846177)
> 
> Wed Jul 25 10:29:15 2007 : Info: IP Allocation FAILED from
general_pool
> (did slogic.t-mobile.com cli 14696825390 port 0 user 14696825390)
> 
> Wed Jul 25 10:29:15 2007 : Info: IP Allocation FAILED from
general_pool
> (did slogic.t-mobile.com cli 14694415538 port 0 user 14694415538)
> 
> Wed Jul 25 10:29:15 2007 : Info: IP Allocation FAILED from
general_pool
> (did slogic.t-mobile.com cli 14696883664 port 0 user 14696883664)
> 
> Wed Jul 25 10:29:15 2007 : Info: IP Allocation FAILED from
general_pool
> (did slogic.t-mobile.com cli 12149915071 port 0 user 12149915071)
> 
> Wed Jul 25 10:29:15 2007 : Info: IP Allocation FAILED from
general_pool
> (did slogic.t-mobile.com cli 19728908614 port 0 user 19728908614)
> 
> Wed Jul 25 10:29:15 2007 : Info: IP Allocation FAILED from
general_pool
> (did slogic.t-mobile.com cli 19723023948 port 0 user 19723023948)
> 
> Wed Jul 25 10:29:15 2007 : Error: Discarding duplicate request from
> client nas01 port 1812 - ID: 102 due to unfinished request 3988
> 
> Wed Jul 25 10:29:15 2007 : Error: Discarding duplicate request from
> client nas01 port 1812 - ID: 62 due to unfinished request 3987
> 
> Wed Jul 25 10:29:15 2007 : Error: Discarding duplicate request from
> client nas01 port 1812 - ID: 116 due to unfinished request 3989
> 
> Wed Jul 25 10:29:15 2007 : Error: Discarding duplicate request from
> client nas01 port 1812 - ID: 121 due to unfinished request 3990
> 
> Wed Jul 25 10:29:15 2007 : Error: Discarding duplicate request from
> client nas01 port 1812 - ID: 26 due to unfinished request 3991
> 
> Wed Jul 25 10:29:15 2007 : Info: rlm_sql (sql): There are no DB
handles
> to use! skipped 0, tried to connect 0
> 
> Wed Jul 25 10:29:15 2007 : Info: rlm_sql (sql): There are no DB
handles
> to use! skipped 0, tried to connect 0
> 
> Wed Jul 25 10:29:15 2007 : Info: rlm_sql (sql): There are no DB
handles
> to use! skipped 0, tried to connect 0
> 
> Wed Jul 25 10:29:15 2007 : Info: rlm_sql (sql): There are no DB
handles
> to use! skipped 0, tried to connect 0
> 
> Wed Jul 25 10:29:15 2007 : Info: rlm_sql (sql): There are no DB
handles
> to use! skipped 0, tried to connect 0
> 
> Wed Jul 25 10:29:15 2007 : Info: rlm_sql (sql): There are no DB
handles
> to use! skipped 0, tried to connect 0
> 
> Wed Jul 25 10:29:15 2007 : Info: rlm_sql (sql): There are no DB
handles
> to use! skipped 0, tried to connect 0
> 
> Wed Jul 25 10:29:15 2007 : Info: rlm_sql (sql): There are no DB
handles
> to use! skipped 0, tried to connect 0
> 
> Wed Jul 25 10:29:15 2007 : Info: rlm_sql (sql): There are no DB
handles
> to use! skipped 0, tried to connect 0
> 
> Wed Jul 25 10:29:15 2007 : Info: rlm_sql (sql): There are no DB
handles
> to use! skipped 0, tried to connect 0
> 
> Wed Jul 25 10:29:15 2007 : Error: Discarding duplicate request from
> client nas01 port 1812 - ID: 105 due to unfinished request 3992
> 
> Wed Jul 25 10:29:15 2007 : Error: Discarding duplicate request from
> client nas01 port 1812 - ID: 74 due to unfinished request 3993
> 
> Wed Jul 25 10:29:15 2007 : Error: Discarding duplicate request from
> client nas01 port 1812 - ID: 29 due to unfinished request 3994
> 
> Wed Jul 25 10:29:15 2007 : Info: rlm_sql (sql): There are no DB
handles
> to use! skipped 0, tried to connect 0
> 
> Wed Jul 25 10:29:15 2007 : Auth: Login OK: [12146063348] (from client
> nas01 port 0 cli 12146063348)
> 
>  
> 
> I have tried playing with the numbers of threads (I used the current
> radius servers setting to start) and the results are the same.
> 
>  
> 
> Anyone have any ideas?
> 
>  
> 
> Thanks,
> 
> Roy
> 

> - 
> List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
- 
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html