[imp] Horde/IMP performance and system requirements (50k+ accounts)

Dietmar Rieder adrieder at sbox.tugraz.at
Tue Mar 24 09:23:06 UTC 2009


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

LALOT Dominique wrote:
> 
> Also, you'll have to look at mysql. For big databases, you need special
> tuning as default values are not good. We are in he way to put (for HA)
> another mysql server and we will split the access to several servers.
> (replica)
> 
> As I reread your mail, look at your SQL setup..

That's exactly what helped us. After tuning the mysqld config the load
dropped to a normal level.
Here as an extract of our my.cnf:

[...]
skip-external-locking
skip-thread-priority
key_buffer = 64M
max_connections = 1024
max_connect_errors = 1000
max_allowed_packet = 8M
table_cache = 512
sort_buffer_size = 12M
read_buffer_size = 1M
read_rnd_buffer_size = 2M
myisam_sort_buffer_size = 64M
thread_cache_size = 64
query_cache_size = 128M
tmp_table_size= 1024M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 12

wait_timeout = 75
interactive_timeout = 75

log_slow_queries
[...]

Try playing with the sort_buffer_size and tmp_table_size, increasing it
helped in our case.
We also configured Horde to not use persistent mysql connections.

maybe it helps.


Didi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFJyKZ15UTx/TQx0LARAoHoAJ0WcGsktBb4w/mv6Sd/plztVlEUbwCgrm+j
/RWVXxC3bwfa4gyiX5Qq4rQ=
=vx74
-----END PGP SIGNATURE-----


More information about the imp mailing list