Hi all, Not being a MySql guru, I figured I'd see if someone here had any thoughts to this issue.
I'm developing freeradius with mysql support to replace our aging cistron radius, which is currently logging accounting data to flat files. Now I'm setting up freeradius with mysql support to handle my authentication and accounting, but the more I think about it, the sheer size of the radacct table gives me worries. Looking at my old accounting log files, I figure the radacct table would grow to about 25,000,000 rows in about a year time. Can mysql handle this? Won't inserts and updates and selects start getting really slow? Are there any mysql table types I should be using for the radacct table? Any kinds of optimizations I will need to perform? Any other cool database/mysql tricks I could use? What are solutions some of you out there haved used to address this situation. I know there has to be others out there with as big or bigger accounting tables. I'd like to have a solution to this now, rather then wait 6 months after deployment and have freeradius grind itself to a halt. Thoughts? ps, is there any time frame when this archive will become searchable? It's really tough to find out if issues have already been addressed without being searchable. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
