Make WordPress Core

Opened 19 months ago

Last modified 15 months ago

#57366 new defect (bug)

WP 6.1 - Performance Regression

Reported by: galapogos01's profile galapogos01 Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 6.1.1
Component: Cache API Keywords: dev-feedback
Focuses: performance Cc:

Description

Hi team,

I am experiencing some significant performance regression when I upgrade from 6.0 to 6.1 (and 6.1.1). Page load time roughly triples across the site.

I do not have a profiler running but using Query Monitor I can see a significant increases in object cache hits (14k to 110k). I understand this is partially expected due to the caching improvements.

I am running a fairly large (170k posts) site with Woocommerce and a number of plugins.

I am happy to provide more detailed analysis but not sure what is the best profiling tool or method to understand where the regression is coming from. If you can provide some guidance I will try to collect more data.

Thanks,
Jason

Change History (4)

#1 @costdev
19 months ago

  • Keywords dev-feedback added

#2 @galapogos01
18 months ago

Hi team, can I please get a little guidance as to how to better document this issue? I am falling behind in versions as I can not run 6.1 in Production. Thanks.

#3 @spacedmonkey
15 months ago

@galapogos01 Have you upgraded to WordPress 6.2? Are you still seeing the same issues?

#4 @galapogos01
15 months ago

I have and I am.

Through some profiling I managed to narrow down the issue to the popular Enfold theme. It had an issue with textdomain initialisation that only showed up where a translation was missing, which happened to be in my case (en_AU). Subbing in a translation file, or their hotfix (documented at https://kriesi.at/support/topic/wp-6-1-enfold-performance-issue/#post-1404110 ) bought page load times down ~3x.

Even after this fix I am finding the theme is measurably slower on 6.1+ than it is on 6.0.1. I was expecting page load improvements - still very unsure about taking this into Production.

Cheers, Jason

Note: See TracTickets for help on using tickets.