Hey @simonbbs – it sounds like you’ve done some extensive testing – thank you. In my testing of a brand new site with just the Classic Editor active I’ve been unable to recreate the kind of slowness you describe.
In terms of your conflict testing – was the Classic Editor your only plugin active when you had the issue? And was it using one of the default (Twenty Twenty Three/Two/One) themes?
Hey @jordesign
Thanks for the follow up!
I hadn’t gone *as* extensively as you highlighted in my testing yesterday, however, I have this morning.
I switched our dev site to the 2020 theme. Deactivated ALL plugins other than Classic Editor and ran my tests.
With the Default 2020 Theme and only Classic Editor active if I click the “Add New Post” button it takes ~30 seconds to load the new post page, and ~45-60 seconds to actually publish the post when I click “Publish.”
If I make no other changes other than turning off the Classic Editor plugin and I click the “Add New Post” button it takes ~2 seconds to load the new post page, and ~1 second to actually publish the post when I click “Publish”
I have a video that shows the giant spike in New Relic when the Classic Editor plugin is active and I try to create a post, versus the negligible impact we see in New Relic when the Classic Editor plugin is not active.
That video does provide a stack trace for both tests in New Relic, however, I’m a little hesitant to supply backend screenshots / videos on a public forum.
Is there a private way I can pass that to you?
One last test I ran as I was finishing typing this response: We were on WP version 6.1.1 when I ran all of the referenced tests and filmed that video.
Just to rule it out I did update WordPress to 6.2.
I see the same behavior when running the same tests on WP 6.2.
Thanks so much!
-Simon
Hey @jordesign
You can view the video with the stack traces at the link here: https://vimeo.com/820528854/09c0447824?share=copy
Thanks so much!
-Simon
Hi @simonbbs just checking if you are still experiencing this issue, I tried to access the video but I need a password.
Hey @thelmachido,
That video was removed as we tracked things down.
The issue was not specifically related to Classic Editor, but rather the “SELECT wp_sorb_users.ID,wp_sorb_users.user_login,wp_sorb_users.display_name
FROM wp_sorb_users INNER JOIN wp_sorb_usermeta ON ( wp_sorb_users.ID = wp_sorb_usermeta.user_id ) INNER JOIN wp_sorb_usermeta AS mt? ON ( wp_sorb_users.ID = mt?.user_id )” db query.
That issue went away when we deactivated Classic Editor as the Gutenberg editor does not try to pull in the author list on the post screen.
The Classic Editor plugin was a false alarm, however, it did help us track down and optimize that slow query.
Thanks so much!
Hi @simonbbs thank you for the update, I am glad you managed to figure this out. If you have any questions feel free to reach out on forums