I agree, but without knowing what type of system he's using or resources he has, it's hard to determine why he's having so many issues.
From his forum:
Good ideas of course - this is all on linux and I certainly could use Ramdisks (or mysql memory tables). I would love to fit the stats tables into Ram but without removing host data and potentially freeing up some other types of data I would need at least 64Gb Ram and more likely 128Gb which would require some high end hardware.
I currently have 32Gb on the DB server which is the max for that particular motherboard.
Here is what I've posted in our private thread.
I have TWO separate databases on two distinct SSD drives.
All updates and calculations are done in the dcfree database to tables name like temp_boinc_user, temp_boinc_team etc etc.
Second database (stats) contains the web facing data with tables named boinc_user, boinc_team etc etc.
Once all updates are done in a single iteration, I copy the database 'files' from dcfree to stats (outside of mysql), so stats then contains both boinc_user and temp_boinc_user. I then drop boinc_user and rename temp_boinc_user-> boinc_user.
This operation is pretty much instantaneous so anyone doing an update on the webpages never tries to access a table that is locked for update.
Problem being though that I write 30Gb of data to the 'stats' drive 20 times per day. That on top of the reads just wears them down.
I could lower the frequency considerably.
I'd love to have the whole 'stats' database in memory personally, but would need 128Gb Ram likely be able to do that (totally new hardware) and it would take some rewrite. (Or remove the hosts part)
Probably other options, but I'm open to suggestions.
*EDIT* this one was an Intel SSD as well which are supposed to be the most robust. Lasted only 5 months.
So I guess he wants to keep it so the site doesn't have any downtime...