Bill: Optimize the wp_options Table of WordPress Database (reduce autoload volume)

The important reason why the Wp_options table becomes huge: the useless RSS feed Cache. If you find a large number of option_name containing "_transient" data in the Wp_options table, it is not running. Let's talk about what this thing is for, this is the cache that is generated after the introduction of RssFeed in the WordPress program. Normal WordPress Use process, will continue to produce these data, over time, it is very large. At this point we have to clean up regularly, the optimization is very simple, in the phpMyAdmin in the Wp_options, execute the following MySQL statement:

DELETE  from WHERE ' _transient_ '

To finish the above results, is wp_options body positive speed reduction (the normal newly installed WordPress wp_options at least 120 is their own). Before I do it is 400+ item, my db.sql.gz backup size is 436kb, after optimization, the remaining 168 items, db.sql.gz backup size is: 320KB, of course, db.sql.gz is present in other tables. Can reduce the 100kb, also is a small progress.

Bill: Optimize the wp_options Table of WordPress Database (reduce autoload volume)