Page MenuHomePhabricator

Flow: VE takes significant time to manifest
Closed, InvalidPublic

Description

We have been encountering a number of performance issues and race conditions with VE and Chrome in recent times, this is probably one more of those.

  • Enter a Message topic

The VE controls and CE field take significant time to appear while the user sees a spinner. For an example causing a failure in a browser test, see https://wmf.ci.cloudbees.com/job/Flow-en.wikipedia.beta.wmflabs.org-linux-chrome/12/testReport/(root)/Create%20new%20topic%20logged%20in/Add_new_Flow_topic/ . Note the test times out with the spinner still visible after 5 seconds.

This is not seen in Firefox


Version: unspecified
Severity: normal

Details

Reference
bz55766

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 22 2014, 2:38 AM
bzimport set Reference to bz55766.
bzimport added a subscriber: Unknown Object (MLST).

The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/324, but people from the community are welcome to contribute here and in Gerrit.

This is likely a problem with the Labs instance; no varnish == no caching of VE elements :/. Unfortunately that means it's something we're probably not going to be able to track or test properly until we go into deployment on production. Closing as WONTFIX since LATER is no longer available.

("RESOLVED LATER" was replaced with the "lowest" priority. Might want to use that instead.)

Aha; thanks for letting me know :).

I've tested it on my own box. It's this call that takes the long time:

'http://localhost/mw-dev/load.php?debug=false&lang=en&modules=ext.visualEditor.base%2Ccore%2Cdata%2Cicons-vector%2Cstandalone%7Cext.visualEditor.viewPageTarget.icons-vector%7Coojs%2Coojs-ui%2Crangy%7Cunicodejs.wordbreak&skin=vector&version=20131106T030133Z&*'

This typically returns in ~6 seconds. However, I've found that sometimes it works in ~200ms. When that happens, VE loads quickly on my local box.

So it does indeed seem to be caching, of a particular ResourceLoader resource.

We removed the VE option in Flow long, long ago :)

People should feel free to reopen this when we actually have the VE in Flow option up and running again.