News for hackers. Stuff that matters.

A comment on MySQL 8.0: Retiring Support for the Query Cache. Parent comment

Re:MySQL 8.0: Retiring Support for the Query Cache by sciurus on Tuesday May 30, 2017 @01:55PM (#14447128)
Primarily by putting a caching proxy server like Varnish in front of Wordpress.
[ Parent | on HN ]
Re:MySQL 8.0: Retiring Support for the Query Cache by agrajag on Tuesday May 30, 2017 @04:12PM (#14448173)
Yep, this is what we do. Adding in some kind of object cache cluster wasn't a significant enough of an improvement over just hitting mysql to justify the extra point of failure.

The problem is WP just makes a ton of simple queries - in any complex install the bottleneck is probably going to be network latency to the database.

[ Parent | on HN ]
Re:MySQL 8.0: Retiring Support for the Query Cache by morgo on Tuesday May 30, 2017 @04:22PM (#14448239)
I think this echo's Rene's point about moving the cache closer to the application as well.

I have some hypothetical numbers illustrating the impact of network latency: http://www.tocker.ca/2013/11/18/how-important-is-it-to-merge...

The simple queries are basically free once they get to MySQL. Query cache does not help.

[ Parent | on HN ]