Hi Mike, Fist of all I would advise you to upgrade that FreeRadius. The 2.12 has some serious bugs. About the MySQL, with 5.5 I would have a look at partitioning; if we are talking about performance problems, there is also Sharding. With some thought you can do the partitioning by month. Be aware of the diferences of the queries before doing that. We are using partitioning here. Regards, Rui Ribeiro pt.linkedin.com/pub/rui-ribeiro/16/ab8/434/
Date: Wed, 21 May 2014 15:23:46 +0000 From: Mike Poole <mpoole@pavlovmedia.com> To: "freeradius-users@lists.freeradius.org" <freeradius-users@lists.freeradius.org> Subject: MySQL Accounting records advice Message-ID: <6712C775E82EB247807B5D7CCFBE940786B23393@sula.pavlovmedia.corp> Content-Type: text/plain; charset="us-ascii"
Using FreeRADIUS 2.1.12 with MySQL 5.5.
Not a freeradius request per se but just wanted to know if others have ideas on accounting records in sql.
We've a mid-size ISP and recently turned on accounting writes to SQL for CALEA. The table has grown enormously and now dwarfs our other databases (20+ GB in about three months).
Has anyone run into this and did you solve it? I'm thinking we should be archiving the table and clearing it out on a regular basis either to a file share or mysql ARCHIVE engine db.
Perhaps even changing the way we do accounting in mysql would be better. A lot of what we do is constrained by mgmt so not always the most efficient.
Thanks for your help. Freeradius has worked great for us!
Mike