Jump to content

Topic on Talk:Contributors/Projects/Editing performance

Post-load performance: Unusable.

3
Alsee (talkcontribs)

When I try to load EN:Intercollegiate_sports_team_champions in the 2017Editor the timing stats between the first to last requests have been {30,33,33,35,40} seconds. The editor is theoretically accepting input, however the actual time elapsed is OVER ONE HUNDRED SECONDS before I can actually get one new character to show up. And when I do type one character, the CPU thread chokes at maximum for over a minute. Then I can type one more character, and the browser goes unresponsive for another minute. Every character locks up the browser for over a minute.

On a smaller article such as EN:New_York_(state) the editor theoretically works, however it's still incapable of realtime response. It can't keep up with even moderate typing speed. Nothing shows up as I type, until the screen updates for a half-dozen keypresses at a time. That is not usable.

Matma Rex (talkcontribs)

I filed a bug about this when I saw your comment (T188965) and investigated quickly. The problem was actually noticed by another engineer (Ed) a few days before and already fixed.

Some code verifying the correctness of operations on the document, that was supposed to run only inside the test suite, was running during normal editing, and that was the reason for the insane slowness.

The fix is live on the Wikimedia wikis already, so you can test it yourself. The typing performance is still poor for long articles, but no longer completely unusable.

Alsee (talkcontribs)

@Matma Rex sorta-thanks. The slow typing is fixed.

However, testing EN:Intercollegiate_sports_team_champions in two different browsers (Chrome and a Firefox variant):

  • Time to load to first editable state is poor compared to the normal wikitext editor (almost 14-20 seconds) to awful (over 40 seconds).
  • The sequence CTRL-A CTRL-X is unusable (time out error and over 40 seconds) to stupid-unusable (multiple time out errors and over 2 minutes).
  • CTRL-V (pasting the original content back into the empty editor) is completely broken. In both browsers I waited over 5 minutes and umpteen time-out errors, then I had to kill the tabs.

The real bug is whoever forced the 2017Editor to be a mode inside of Visual Editor.

Reply to "Post-load performance: Unusable."