very weird jamminjames as Autoptimize (or nginx or cache enabler) do not optimize the backend. what I would suggest; install query monitor and see what that (great) plugin says is slowing things down?
frank
have you had the opportunity to see what Query Monitor reports @jamminjames ?
Sorry for the slow reply. I installed Query Monitor, and it pointed out that I had APCu installed, but needed a WordPress plugin to get it working with WordPress. I installed APCu Manager, and it’s working, and the backend seems a bit faster. Still slower than it should be, seems to me.
The Query Monitor reports that for “slow queries”, WordPress Core shows up every time I’m editing a post, with a query like:
SELECT DISTINCT meta_key
FROM siow8zcap_postmeta
WHERE meta_key NOT BETWEEN '_'
AND '_z'
HAVING meta_key NOT LIKE '\\_%'
ORDER BY meta_key
LIMIT 30
There are also 19 duplicate queries.
I use the Classic Editor, not sure if that’s a problem when it comes to speed.
the problem likely is a too big a postmeta table, making the query slow. it is part of wp-admin/includes/template.php, meant to get custom fields on a post/page edit screen, see https://github.com/WordPress/WordPress/blob/464026afbc077a967b72a05e1eeb5d7c5d3edd11/wp-admin/includes/template.php#L683
Yes, looking into it, there are certain plugins that seem to record the same info over and over again, using the same keys. I am trying to reach those plugin authors. Thanks for the help.
-
This reply was modified 2 years, 8 months ago by
jamminjames.
