You can also use "sizer" to capacity plan. It will calculate the size of
the current database and you can get the data into an excel spreadsheet.
This way you can increase the number of records you have in various tables
and see the resulting DataMemory/IndexMemory usage.
On Mon, May 21, 2012 at 4:20 PM, Antonio Modesto <modesto@stripped>wrote:
> On Mon, 2012-05-21 at 18:04 +0400, Alex/AT wrote:
> > > I work at an ISP and we're going to put a mysql-cluster in
> > > as our Freeradius backend, as you know the radius database always keeps
> > > growing because of the accounting, and I want to estimate the maximum
> > > size it could reach, how can I know how much my cluster can store?
> > I may recommend you to make multilevel accounting archive (we do). Store
> > active sessions in Cluster and after they close, move them to archive
> > (presumably partitioned InnoDB). Of course, this will require some
> > modifications to billing/accounting/tech systems to select data from both
> > the Cluster and archive, but it's worth the effort.
> It seems to be a nice idea, although I have no idea from where to start
> (laugh). Do you periodically run some sort of script reading the radacct
> table searching for closed sections, removing and inserting them in a
> InnoDB table? Or is it something that executes in realtime?
> MySQL Cluster Mailing List
> For list archives: http://lists.mysql.com/cluster
> To unsubscribe: http://lists.mysql.com/cluster