I have a PHP based app service which allows a load of tablets on a LAN to communicate with each other. Everything is stored in mySQL with around 100 queries a second
The database never exceeds 50MB in size. The app only runs for 4 hours.
It's a pile a crap, there is no budget for a rewrite, currently the server struggles with the load, going to a higher powered server isn't an option as it needs to be remotely portable.
Currently using an i7 with 16GB ram and 128GB SSD.
Anyway my question, is there a way to easily run the mySQL database from memory and only have writes touch the disk?
This will also use mySQL replication across two servers for basic fail over.
While I understand running it in memory like this is probably very bad, but currently I see no other option for a quick fix. Looked into memcached, not an option due to the time it would take to implement and test.
Also looking into using opscode caching for PHP to speed things up a little
The database never exceeds 50MB in size. The app only runs for 4 hours.
It's a pile a crap, there is no budget for a rewrite, currently the server struggles with the load, going to a higher powered server isn't an option as it needs to be remotely portable.
Currently using an i7 with 16GB ram and 128GB SSD.
Anyway my question, is there a way to easily run the mySQL database from memory and only have writes touch the disk?
This will also use mySQL replication across two servers for basic fail over.
While I understand running it in memory like this is probably very bad, but currently I see no other option for a quick fix. Looked into memcached, not an option due to the time it would take to implement and test.
Also looking into using opscode caching for PHP to speed things up a little