High Performance Wordpress
Download as PPT, PDF7 likes3,032 views
The document outlines strategies for optimizing WordPress performance, emphasizing speed, server scalability, and effective configuration of the LAMP stack. It highlights the importance of tuning Apache, MySQL, and PHP settings, managing plugins and themes, and utilizing CDNs for caching. Additionally, it discusses more advanced setups like MySQL replication and using Varnish for serving content from memory.
High Performance Wordpress
- 1. High Performance WordPress Gareth Davies
- 2. Why performance? Speed so people don’t wait Scale serve as many requests to as many people as possible, concurrently
- 3. LAMP A stack LAMP Linux Apache MySQL PHP
- 4. WordPress Written in PHP Uses MySQL as the database Apache/nginx can be used for HTTP
- 5. WordPress Core (installed) Themes Plugins
- 6. OS Level Tuning You’re 64-bit by now Log errors, and nothing else TCP/IP settings Only run services that you need on a server
- 7. OS Level Tuning Simple firewall to stop bots Read log files from logwatch -- hardware dies too vmem.sh Filesystem - XFS is best, EXT3, EXT4 are OK too
- 8. Apache Tune Apache (httpd.conf) ab & httperf MaxClients Defaults are usually horrible
- 9. MySQL Defaults are terrible, use my.cnf mysqltuner.pl, tuningprimer.sh mytop Use maatkit + mk-query-digest See general & slow query log (for your plugin problems) InnoDB is better for concurrency, though by default you’re probably using MyISAM mysqlslap for benchmarking
- 10. PHP Memory settings Opcode cache XCache, EAccelerator, APC php.ini
- 11. WordPress Plugins are often horribly coded Themes can have direct calls to the database
- 12. WordPress Look at wp_options tables Disable plugins Try the new Twenty Ten theme wp_config.php: WP_HOME, WP_SITEURL
- 13. Still struggling? Content Delivery Networks (CDN) Minify Caching
- 14. WP Caches WP Super Cache W3 Total Cache
- 15. More you can do use mod_proxy and serve static content CDN: Amazon S3+CloudFront is affordable use browser cache (set long expires)
- 16. Separate machines 2 machines web server database server memcached servers?
- 17. Varnish Varnish serves everything from memory httpd on a different port, run varnish on port 80 and point it to httpd port
- 18. Further growth Its now time to think about MySQL replication (master-slave setups) memcached to keep caches of query results (up to 1M) in memory HyperDB supports data partitioning, and can read from multiple databases
- 19. WordPress.COM several billion HTTP queries per day, billions of MySQL queries too HP hardware, all SSD
- 20. HipHop from Facebook http://huichen.org/en/2010/06/wordpress-3-benchmark/ http://huichen.org/en/2010/06/wordpress-3-benchmark-part-2/ ~2.7x improvement in performance
- 21. Find Me @ShaolinTiger on Twitter http://www.shaolintiger.com – My Blog shaolintiger at gmail – Email me