... there are many ways and which is the best for you depends of your setup ...
Generally i would say, if you don't have a dedicated DB server and additional a very slow I/O (HDD),
you could use some of your left RAM for DB speedup.
Some InnoDB settings allow you to adapt buffer size and other important params.
A very powerful speedup is setting up a RAM-Disk for the transaction log files.
This saves a lot of I/O accesses, but is a bit more unsafe and not recommended if your server crashes often.
If you are really brave, you can (a really stable system assumed) hold the whole DB files in RAM-Disk.
This is very fast but dangerous too and you need procedures to save and restore your files from/to HDD at server start and before shutdown.
Do you have "broken leg" problems too? If yes, did you try the latest publicEH.sqf?
Generally i would say, if you don't have a dedicated DB server and additional a very slow I/O (HDD),
you could use some of your left RAM for DB speedup.
Some InnoDB settings allow you to adapt buffer size and other important params.
A very powerful speedup is setting up a RAM-Disk for the transaction log files.
This saves a lot of I/O accesses, but is a bit more unsafe and not recommended if your server crashes often.
If you are really brave, you can (a really stable system assumed) hold the whole DB files in RAM-Disk.
This is very fast but dangerous too and you need procedures to save and restore your files from/to HDD at server start and before shutdown.
Do you have "broken leg" problems too? If yes, did you try the latest publicEH.sqf?