I have seen a lot of “turn of auto-save or clutter up your database”-type comments lately claiming the auto save function in WordPress will waste a lot of space in the database. In reality, this is not the case.
There is a lot of debate going on about the new EU law regarding cookies; how they are used and when they need explicit consent from the end user to be used. Some people claim that sites will be cluttered with warnings and popup windows and therefore will give an advantage to competitors in non EU locations. It is my belief that this is a common misconception and misinterpretation of this new directive.
I recently wrote about Moving WordPress into RAMÂ to gain a significant performance boost. This is however a bold move and there are a lot of other things you can do to gain performance, one of them is using a newer version of MySQL (and why not take a look at Percona Server?).
There are a lot of things you can do to optimize WordPress to run as smooth as possible including optimizing Apache and MySQL, introducing cache layers and more. That is just fine, and they should be done in a production environment. In a development environment however, it is another story. Here you have the option to do radical things for radical results. Like, moving all data into RAM!
RECENT COMMENTS