VIVO Documentation
Page History
...
Panel |
---|
From Mark at Griffith Uni - We use an enterprise hosted MySQL ie. remote to our vivo server via gigabit ethernet. In this configuration we have found MySQL to be a real performance bottleneck. Here are some parameters that we have found it worthwhile experimenting with: innodb_flush_log_at_trx_commit=2
tmp_table_size max_heap_table_size key_buffer_size (needed because many of our queries include a group or sort) |
Writing the MySQL transaction log
MySQL allows you to control its logging behavior, using the the innodb_flush_log_at_trx_commit
parameter. On some systems, changing the value of this parameter can dramatically improve performance.
...
If performance is abysmal on a simple query, check for missing or corrupted MySQL indexes that may cause the query engine to do full table scans.
TCMalloc and MySQL
Interesting GitHub blog post (https://github.com/blog/1422-tcmalloc-and-mysql) describing debugging MySQL performance issues, and using tools like the open source Percona Toolkit and the Google-contributed TCMalloc from gperftools.
Overview
Content Tools