On Wed, 28 Jul 2004, Jorge Cuevas wrote: > Hello, > > I have accounting of aprox. 5000 concurrent calls, and I am storing only > stop accounting packets in Mysql. > Does anybody have any good recommendations on the tuning of mysql and > freeradius?
See doc/tuning_guide Make sure that the queries run on accounting stop processing only need to examine one or two rows (you can use EXPLAIN SELECT for that). As stated in the tuning guide: "Add AcctUniqueId in the accounting_stop query. Especially if you have a lot of access servers or your NAS does not send very random Session-Ids. That way you will always have one candidate row to search for, instead of all the rows that have the same AcctSessionId" I pressume you are using mysql with innodb. Tune innodb parameters (see the mysql manual for that). In general mysql should work ok if the queries run do not map to many candidate rows. That's the most important part. Set noatime on the partition holding your sql tables (if haven't done that already). > > Right now I have divided loads on different accounting ports (2 now, > thinking of 3), max_servers of 256 on radiusd.conf on each > configuration and 200 num_sql_socks in sql.conf > > The machine is a dual xeon with 2GB Mem > Running Redhat 8 with kernel 2.4.18-14smp > > Thanks > > -- > Jorge > > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > -- Kostas Kalevras Network Operations Center [EMAIL PROTECTED] National Technical University of Athens, Greece Work Phone: +30 210 7721861 'Go back to the shadow' Gandalf - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
