2014-02-12 12:32 GMT+01:00 Lukas Lehner <weblehner@stripped>:
> Hi Antonio
> all tables use InnoDB. The size is 27 GB (not yet in prod). I guess in prod
> it will be fast 80GB.
Depending on how your application is going to use MySQL resources you will
need to tweak some things (and not only MySQL).
If it is going to be CPU bound, IO bound etc...there are different scenarios
Anyways, some general things to take a look at:
- Use file per table if possible. This won't give you extra performance,
but it will be good if you run into disk spaces issues or for future table
- Make sure you have trx_commit and sync_binlog disabled (make sure you
understand what this means and what problems you could have during an un
- If you're expecting lot of temporary tables (filesorts), make sure tmpdir
runs over a fast disk.
- Use NUMA memory handling
- Make sure you test different disk schedulers (depending if you have RAID
and which kind of it) and see how they perform.
- You might want to take a look to smp irq affinity and see how it could
impact in your system.