> hi mike,
>
> you and the rest of ian's group did a noble job by optimizing and saving
> some resources between the radius daemon and the external program by making
> a gateway or bridge by using of your radius helper daemon. regarding to onie
> case and he is using a mysql database as a backend, assuming he is using
> your radius helper daemon, the bottleneck that i saw is between the external
> program and the mysql daemon. every time a external program communicate to
> mysql daemon, it will open a mysql database file, queries it and close the
> database file when its done. the time to open and close a database file is a
> big factor in terms of performance especially when your metric is request
> per second. :-> maybe this is a another big challenge to ian's group to
> create a helper between the external program and the mysql or any database
> server as what your group did between the radius daemon and the external
> program.
>
Actually, our radius helper just preloads a perl script, which you can define
yourself. You can make it inefficient by opening and closing the connection to
the database each time there is a request for auth/acctg, or you can make the
connection to the database persistent, in which case there is no added overhead
of opening and closing the database..
Note that since it's all in the perl script, you don't have to have your data
in a database. You can use DBD::CSV and store your users on a ramdisk, if you
like blinding speed. Just make sure to have a good UPS or sync regularly to a
disk file!
\8)
-
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
