Last modified: 2014-02-12 23:39:57 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T47267, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 45267 - Opening diff [Working ...] is extremely slow, apparently client-side
Opening diff [Working ...] is extremely slow, apparently client-side
Status: NEW
Product: Wikimedia
Classification: Unclassified
Git/Gerrit (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
https://gerrit.wikimedia.org/r/#/c/50...
: performance
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-22 06:59 UTC by Nemo
Modified: 2014-02-12 23:39 UTC (History)
6 users (show)

See Also:
Web browser: Firefox
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Nemo 2013-02-22 06:59:51 UTC
This is a general problem, quite visible in the URL: it take 22-25 s to open for me in Firefox and about 5 in Chromium, counting from when "Working ..." is displayed.
Given that top shows a lot of CPU usage during the diff loading and that there's such a difference between browsers, I suppose this is a client-side problem, but I hope something can be done about it, because MediaWiki volunteer contributors may not have the resources to overcome it.
I have a recent but not so quick CPU (AMD E350) and a core was free for use by the browser.

This is not bug 40793 because https://code.google.com/p/gerrit/issues/detail?id=1370#c1 doesn't help it.
Comment 1 Chad H. 2013-02-22 11:49:31 UTC
The issue in Firefox might be slightly related to 35860? I'm unable to replicate any problems with Chrome :\
Comment 2 Nemo 2013-02-22 12:42:19 UTC
Nope. I don't see any particular memory consumption when opening the diff.
It's the same on Chrome as on Chromium here (no surprises).
Comment 3 Marcin Cieślak 2013-02-23 13:09:47 UTC
6 seconds of "Working..." time on Mozilla/5.0 (X11; FreeBSD amd64) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.57 Safari/536.11 on a definitely not recent CPU.
Comment 4 Nemo 2013-05-14 17:10:13 UTC
I can't find this filed upstream, is it still outside the radar? I doubt I'd be able to submit a very useful upstream report on performance issues.
Comment 5 Nemo 2013-05-14 17:18:00 UTC
Worst case is usually MessagesEn.php, in my experience: https://gerrit.wikimedia.org/r/#/c/58049/3/languages/messages/MessagesEn.php takes 47 s on Firefox and 5 on Chromium.
It's not only about size, because this file is 400 KB (vs. 300) and diff is almost instant: https://gerrit.wikimedia.org/r/#/c/63422/2/wmf-config/InitialiseSettings.php
Comment 6 Siebrand Mazeland 2013-06-28 05:50:13 UTC
Yesterday evening the observed behavior caused Gerrit to no longer be usable for me in Firefox. It should definitely be filed upstream somewhere.
Comment 7 christian 2013-06-29 12:40:06 UTC
(In reply to comment #6)
> Yesterday evening the observed behavior caused Gerrit to no longer be usable
> for me in Firefox.

As comment #6 seems to be different …
If it was not only slow, but did not stop at all to load in Firefox, it may be
a caching problem. You could try the remedy described in bug #50309.
Comment 8 Siebrand Mazeland 2013-07-04 09:31:52 UTC
Also per bug 50309: With some updates in how Gerrit was installed, this has been resolved. One of the two issues should probably be duped.
Comment 9 christian 2013-07-04 13:01:54 UTC
The URL given in the bug description:
  https://gerrit.wikimedia.org/r/#/c/50040/3/MoodBar.i18n.php

Still takes ~11 seconds to load for me (~9 seconds doing computations on
the client side). To me, they still seam to be separate issues.
Or maybe I should just buy a beefier computer :-)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links