Last modified: 2013-06-27 21:42:44 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 T50884, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 48884 - Gerrit slow lately
Gerrit slow lately
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Git/Gerrit (Other open bugs)
unspecified
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-28 07:58 UTC by Niklas Laxström
Modified: 2013-06-27 21:42 UTC (History)
7 users (show)

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


Attachments

Description Niklas Laxström 2013-05-28 07:58:29 UTC
Gerrit has been slower than before for the past week or so.

Symptoms:
* Loading my dashboard can take 15+ seconds (subsequent reloads are faster, which indicates that it is cached)
* Similarly loading commits or changes filed sometimes take a long time
* git pull/review times out - especially annoying when updating mediawiki extensions when you might need to rerun the script multiple times, and it messes up the l10n-bot.

I'm seeing the first two all around the days, while the last one seems to happen usually in European evenings - perhaps these two are not related but for now I am assuming they are.
Comment 1 christian 2013-05-31 22:45:37 UTC
There were several reports on gerrit becoming slowish for other sites as well (e.g.: [1]). Upstream is working on it. There is at least one bug in jgit that
they are hunting down.

By what I've read, restarting gerrit seems to fix this kind of problems for
some time.

If we restart gerrit, could someone with access to this data please at least grab show-{chaches,connections,queues}? Since gerrit reported database connection problems at some other point, it would also be interesting to see statistics on the database side.


[1] https://groups.google.com/forum/?hl=en&fromgroups#!topic/repo-discuss/jN8TElfgCtM
Comment 2 Andre Klapper 2013-06-18 07:14:53 UTC
(In reply to comment #1)
> If we restart gerrit, could someone with access to this data please at least
> grab show-{chaches,connections,queues}?

CC'ing Hashar (Chad is already CC'ed), though I wonder if this still happens?
Comment 3 Antoine "hashar" Musso (WMF) 2013-06-18 09:20:14 UTC
Christan and Chad talked about it yesterday.  I have not closely followed the conversation though.
Comment 4 Chad H. 2013-06-27 14:47:26 UTC
There's nothing really specific we could ever unearth here. I'm going to mark this as fixed with the 2.7-rc2-505-g7502a46 deployment (which contains about a billion improvements to everything).
Comment 5 Antoine "hashar" Musso (WMF) 2013-06-27 21:04:14 UTC
The l10n submissions tonight seems to have worked well as far as Zuul is concerned. So yeah, Gerrit looks faster to me :-]
Comment 6 Siebrand Mazeland 2013-06-27 21:09:52 UTC
I had a lot of trouble in Firefox with pages staying "loading..." forever, and no problems at all in Chrome. Out of 10 patch sets opened in firefox that are on my dashboard, no more than 3 or so would eventually display the patch set contents.

Does anyone recognize this?
Comment 7 Antoine "hashar" Musso (WMF) 2013-06-27 21:26:57 UTC
When we started with Gerrit I remember people had issues with Firefox, that might the root cause.  I am myself using Safari and I believe most folks are using Chrome/Chromium nowadays, all those browsers are based on Webkit.

Another issue was the syntax highlighting that cause server side slowness/timeout etc sometime. Specially on huge files such as Title.php or i18n messages files.  I disabled syntax highlighting entirely.

Hope this help.
Comment 8 Nemo 2013-06-27 21:42:44 UTC
(In reply to comment #6)
> I had a lot of trouble in Firefox with pages staying "loading..." forever,
> and
> no problems at all in Chrome. Out of 10 patch sets opened in firefox that are
> on my dashboard, no more than 3 or so would eventually display the patch set
> contents.
> 
> Does anyone recognize this?

Siebrand, this is bug 45267.

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


Navigation
Links