MySQL 8.0: Retiring Support for the Query Cache

Re:MySQL 8.0: Retiring Support for the Query Cache by Viper007Bond on Tuesday May 30, 2017 @02:27PM (#14447324)

If you enable WordPress's object cache, it should get most page views down to a couple or even zero queries. It's poorly written themes and plugins where problems can arise.

The easy solution is to just enable full page caching. On single server setups, something like WP Super Cache works well. On distributed setups like WordPress.com, this is more appropriate: https://github.com/Automattic/batcache

[ Parent | on HN ]

Re:MySQL 8.0: Retiring Support for the Query Cache by tyingq on Tuesday May 30, 2017 @02:34PM (#14447372)

The object cache doesn't persist across HTTP requests. You have to install some 3rd party plugin for that.[1]

[1]https://codex.wordpress.org/Class_Reference/WP_Object_Cache

[ Parent | on HN ]

Re:MySQL 8.0: Retiring Support for the Query Cache by Viper007Bond on Tuesday May 30, 2017 @02:37PM (#14447398)

Correct, which is what I meant by enabling it. Apologies for not being clearer.

It used to persistent via writing objects to the filesystem but it actually ended up being _slower_ in some configurations.

[ Parent | on HN ]

Re:MySQL 8.0: Retiring Support for the Query Cache by munchai on Tuesday May 30, 2017 @08:12PM (#14449612)

Having an object cache is one layer. However, caching SQL in conjunction could speed up application response times, depending on the behavior of the workload. I have seen the performance increase by 4x by caching SQL.

[ Parent | on HN ]