-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extensive articles with over 1700 words and various blocks make Gutenberg very slow. #10418
Comments
Tested on Win10, Chrome Version 69.0 Couldn't reproduce the issue. This is how it worked in spotlight mode: My internet speed is about 15Mb/s |
So I feel like it's getting worse and worse. Here is a new screencast: http://recordit.co/IcDK4Xc6Sb |
And here my internetspeed: http://prntscr.com/l8bz08 |
@designsimply if you want I can send you access data to the website. Which automatic employee can I contact? |
I would like to add one more thing: if I start a new fresh article, then it is going quite well: http://recordit.co/fn7wBBE5sW But if the article is very extensive, then it is very slow and it falters without end (1700+ words and many different block variants). |
This feels like a 5.0 blocker issue that should be looked into. |
I want to give a small update: the editor is getting faster and faster. I don't know what you're doing, but please keep it up. It's not like the old editor yet. But we are already on the right track. I took a new test with the newest Version (5.0-beta3-43867) |
The most important issues causing performance loss are fixed for me by #10723 and the last remaining one is #10427 which is currently being worked on in #7409 and #11267. Since I think the remaining point here is tracked in #10427 I'm going to close this as duplicate. Please if you find other things impacting performance, open follow up issues. |
Thanks for the offer! But requiring a login to other closed systems for the purpose of testing is not a good solution in general. What would be nice, however, would be an export of the content, or content that is very similar, so I may use it for testing. I noticed the content structure screenshot in your original report says the post you are testing has 235 headings+paragraphs and 308 blocks, so I am interested to know how many other kinds of blocks there are and I am wondering how many (if any) of them are classic blocks. I also noticed the post is in German. If you are able to provide the output of More > Copy All Content either in a pastebin or a gist or somewhere I can access it, I will try using it for testing to see what I can find when testing the PRs referenced in the other replies here—which I think would be good to do. |
Hi, I tested it with 4.2 (Plugin only) and it's soooo slow. How can I do that? Ok here is my content:
|
@SchneiderSam I tried out your content on my personal site which is running 4.2 and didn't experience any major issues. I used Safari 12 on macOS Mojave, with an Intel Core i7 processor. It only got slightly slow once I had clicked into a bunch of the blocks (which loads up the RichText component) and even then the lag was still pretty minimal, maybe 0.3–0.5 seconds or so. Did you have any notable errors in your JS console? |
Ahhh. Here's something: http://recordit.co/7RhbEGlCd0 Or should I set something special on the Chrome Console? |
I tested using the content sample provided (thank you!) and found a couple main things: 1/ typing was indeed laggy (I noticed there were 227 blocks which are mostly headings and paragraphs with some lists and about 5 columns blocks—noting this for reference) and 2/ it takes about 6 or 7 seconds to re-open the post after closing it. (2min) I tested with my site language set to German as well as English. Because this issue is a duplicate, I will keep an eye on the related PRs (#10723, #10844, #10723, #11287, #11267) and re-test using this content when those are all resolved so we can close the loop here after the performance updates that are in progress become finished. Thank you again for testing and reporting this! Notes:
This is good info and I am copying a screenshot from that video for reference because all of those warnings about handlers seem relevant and I don't see those in my own testing: Also copying your internet speed screenshot for reference as it's very relevant and making a note for myself do a lot of testing with throttling turned on in browser tools as I go: In comparison, my internet connection is very fast: |
@designsimply Thanks for taking the mistake seriously. That gives you a certainty with all the anti-Gutenberg opinions. |
@designsimply I just want to make a short update to the last Gberg Update 4.3-RC: it's still slow. And this although the related PRs you mentioned should be fixed to 4.2 / 4.3. I think it still hangs somewhere... |
I tested it today with the content provided by @SchneiderSam and the problem persist for me. I tested it with Firefox in the current RC as well as with the nightly build plugin and wp 4.9.8. I also tested it with Chrome. There it lags a bit as well, but not as bad as with Firefox. Here is a screencast with my xp: https://www.youtube.com/watch?v=yIV6REWM5tE |
Describe the bug
If the spotlight mode is activated (or any other mode) and you jump between paragraphs, it always takes a while. This is only a fraction of a second, but depending on your internet connection or whatever, it can interfere with the writing flow.
I don't have the fastest Internet connection, but the problem only occurs in different modes when the article is very extensive. There is always a slight delay, which interrupts the write flow. I think this is especially interesting for countries that don't have such a fast internet connection. But I'm not sure if this is the reason. In any case there is a little delay.
I would like to add one more thing: if I start a new fresh article, then it is going quite well: http://recordit.co/fn7wBBE5sW
But if the article is very extensive, then it is very slow and it falters without end (1700+ words and many different block variants). The more I write, the slower Gutenberg gets.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A faster change within the blocks and a smoother writing flow. This only happens when the article is very extensive.
Screenshots
http://recordit.co/LzOYawwJYI
Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: