Last modified: 2013-04-03 20:34:01 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 T48399, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 46399 - "Included in" is very slow
"Included in" is very slow
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Git/Gerrit (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Chad H.
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2013-03-21 02:43 UTC by Matthew Flaschen
Modified: 2013-04-03 20:34 UTC (History)
6 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Matthew Flaschen 2013-03-21 02:43:23 UTC 
This may be an upstream issue, but Gerrit's "Included in" feature (showing the branches that include a commit) is consistently very slow on core (which I realize is a big repo and has many branches).

I timed the AJAX call for it on https://gerrit.wikimedia.org/r/#/c/52459/, and it was 2 minutes, 15 seconds.

It doesn't seem to be cached in any way either.
Comment 1 Chad H. 2013-03-21 04:26:13 UTC 
It's been this way for a couple of releases. Probably an upstream thing.
Comment 2 Matthew Flaschen 2013-03-21 06:22:40 UTC 
Are you going to file upstream, or should I?  I don't see it at https://code.google.com/p/gerrit/issues/list?can=2&q=%22Included+in%22
Comment 3 christian 2013-04-03 10:48:12 UTC 
After Chad running GC yesterday, I timed the AJAX call as in
comment #1. It's down to 4.33 seconds now (mean of 5 runs,
worst case being 4.85s).

Is that fast enough already?
Comment 4 Matthew Flaschen 2013-04-03 20:34:01 UTC 
Indeed, it's fixed.

I tested with that one as well as others, and I don't think it exceeded 6 seconds once.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links