[Maia-users] InnoDB Database Type?

[Robert LeBlanc]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Papazafeiropoulos Giorgos wrote:

> Suppose that the deletions (expire-quarantine)
> have become too costly due to the volume of the database. And thus the
> relevant script takes too much to terminate. Let's say more than a day.

If an expire-quarantine-cache run is taking you a day to finish, there's
something seriously wrong with your database setup.  Either MySQL is
starving for system resources (e.g. too much system load, not enough RAM
and/or processing power, not enough drive heads, etc.), or it needs to
be tuned to take better advantage of the resources it has to work with.

As a starting point, a number of people on this list have reported great
improvements by tweaking the innodb_buffer_pool_size setting, which
helps MySQL take better advantage of any free RAM you may have.  Try
setting this to 50-80% of your RAM to see a dramatic performance boost.


> Then
> the addition rate can be higher than the removal and the db will always
> grow. It doesn't matter if you decrease the days limit for which you
> keep quarantined items. You
> simply don't delete as fast as you add items. Is there a way to help the
> deletion's in a MySQL database? What other possibilities, apart from the
> cluster , since you don't
> propose it for the Maia system, are to increase the scalability of the
> database?
> I have reached such a limit at the current installation I have done,
> which by now has several hundrends of GBs of quarantined items.

In your case it sounds like you first need to get MySQL tuned properly,
and/or give it more resources to work with.  Once you're able to start
running the expire-quarantine-cache and process-quarantine scripts
again, you can apply a one-time correction to your database by dumping
it and reimporting it.  From there, your equilibrium point should be
much lower.

- --
Robert LeBlanc <rjl at renaissoft.com>
Renaissoft, Inc.
Maia Mailguard <http://www.maiamailguard.com/>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFcCAYGmqOER2NHewRAk5LAJsFUrvKPPQXgZVUWbPVoALcPYZn1gCgoLFa
ghH2/nVVXkDsZbQRhYHh5O4=
=CFeJ
-----END PGP SIGNATURE-----