On Sat, 8 Jan 2005, Torsten Harenberg wrote:
> Okay, that worked w/o and problems, allthough it took several hours to
> finish.
>
> Should this been done regularly? I.e. should I make a crontab entry?
Hi Torsten,
I don't think you need to do it regularly. MySQL should maintain an
approximate index cardinality (which apparently is what the optimiser
needs to know) - although the documentation does state that in certain
circumstances the estimate can become out of date.
[...]
> > which should allow the database to hold up to about 9.5M events. (At which
> > time it will be about 220Gb in size). With the default limit the critical
> > number of jobs is ~550,000.
>
> You really suggest to let the DB grow up to 220 Gigabytes? Wouldn't this
> slow down MySQL even further?
I only mean that with these row limits there is a finite number of jobs
that can be entered into the database. I was estimating the size of the
database on disc at that point. (Infact the actual size can vary depending
on the characteristics of the jobs the RB has handled). I don't mean that
you want to reach this size - although having a large size database
doesn't necessarily imply that MySQL will slow down.
We may need to revise the policy on retention of all the LB data. It is
possible to prune the database and remove old entries. However at the
moment the RB isn't configured to do that, so your database will slowly
grow.
> My RB doesn't have such a large HDD, allthough it would be no problem to
> install one. Is this really needed / suggested?
How are you for free space now? Did you look to see the size of the
individual table files?
Yours,
David
--
-------------------------------------------------------------------------
David Smith e-mail: [log in to unmask] tel: +41 22 76 74462
Address: D. Smith, CERN G06610, Bat 28 R-007, 1211 Geneva 23, Switzerland
-------------------------------------------------------------------------
|