SQL usage ideas

[Roy Walker]

Maybe I am misunderstanding you, but are you saying there is already a method to pull the data from the database and cache it using 'fastusers'?  I do not see anyway to do that...
 
There are a lot reasons to keep the data in a database, look at the NAS table (I realize it is read-on-start for DOS reasons) but someone must be of the same mind set as me or there would be no client support in the SQL module.
 
Roy

________________________________

From: freeradius-users-bounces+rwalker=sensorlogic.com at lists.freeradius.org on behalf of A.L.M.Buxey at lboro.ac.uk
Sent: Sun 7/29/2007 3:42 PM
To: FreeRadius users mailing list
Subject: Re: SQL usage ideas



Hi,
> Well if you understand server/client systems, no client request is INIFINATELY faster than a server cached request.  So when you get to the point where you need to handle several hundred requests a second, you do the math.

depends on how the SQL tables are indexed, how the server is configured
etc etc - certainly I've got some very complex queries that upon benchmarking
against a million entries can run in less than 0.00 (ie MySQL basic
counter in seconds isnt good enough to measure ;-) )

but if you want to take your data, then cache it in memory rather than
query it.....well, that sounds much like having it in memory and not
in a database at all - ie 'fastusers' and the such...rather than a
database as we know it.

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


-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 4720 bytes
Desc: not available
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20070729/b2497e73/attachment.bin>