Last modified: 2014-03-23 02:28:34 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 T64768, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 62768 - CirrusSearch should embed performance data in the page output
CirrusSearch should embed performance data in the page output
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
CirrusSearch (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: performance
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-18 03:57 UTC by Ori Livneh
Modified: 2014-03-23 02:28 UTC (History)
4 users (show)

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


Attachments

Description Ori Livneh 2014-03-18 03:57:04 UTC
To facilitate client-side reporting of RUM, CirrusSearch should embed relevant performance data in the page output.

This could be done by defining a MakeGlobalVariablesScript hook handler, or by adding a call to $out->addJsConfigVars() in CirrusSearch\Hooks::specialSearchResultsPrependHook.

(Please don't use <!-- comments -->; having to parse the data from a comment node sucks.)

As to what data should be sent: Navigation Timing data will tell us the total time it took the user's browser to retrieve and render the search result page, so what we want are figures that can tell us the portion of that time that was taken up by Cirrus. If you want to be very granular, and provide timing data for different parts of the total request processing time, that's fine too.

Please use milliseconds as the unit; fractional milliseconds are OK if you want finer resolution.
Comment 1 Gerrit Notification Bot 2014-03-18 05:27:24 UTC
Change 119235 had a related patch set uploaded by Chad:
Rewrite SearchResultSet::getInfo() to actually be useful

https://gerrit.wikimedia.org/r/119235
Comment 2 Gerrit Notification Bot 2014-03-18 05:27:34 UTC
Change 119237 had a related patch set uploaded by Chad:
Remove current implementation of getInfo()

https://gerrit.wikimedia.org/r/119237
Comment 3 Gerrit Notification Bot 2014-03-18 05:27:35 UTC
Change 119238 had a related patch set uploaded by Chad:
Remove current implementation of getInfo()

https://gerrit.wikimedia.org/r/119238
Comment 4 Gerrit Notification Bot 2014-03-18 19:08:15 UTC
Change 119238 merged by Chad:
Remove current implementation of getInfo()

https://gerrit.wikimedia.org/r/119238
Comment 5 Gerrit Notification Bot 2014-03-19 15:28:26 UTC
Change 119236 merged by jenkins-bot:
Remove current implementation of getInfo()

https://gerrit.wikimedia.org/r/119236
Comment 6 Gerrit Notification Bot 2014-03-19 15:31:06 UTC
Change 119237 merged by Chad:
Remove current implementation of getInfo()

https://gerrit.wikimedia.org/r/119237
Comment 7 Gerrit Notification Bot 2014-03-19 17:03:32 UTC
Change 119503 had a related patch set uploaded by Chad:
Expose search metrics to Javascript for performance tooling

https://gerrit.wikimedia.org/r/119503
Comment 8 Gerrit Notification Bot 2014-03-19 17:05:09 UTC
Change 119505 had a related patch set uploaded by Chad:
Remove completely useless implementation of getInfo()

https://gerrit.wikimedia.org/r/119505
Comment 9 Gerrit Notification Bot 2014-03-19 17:07:36 UTC
Change 119235 abandoned by Chad:
Rewrite SearchResultSet::getInfo() to actually be useful

https://gerrit.wikimedia.org/r/119235
Comment 10 Gerrit Notification Bot 2014-03-20 17:36:55 UTC
Change 119503 merged by jenkins-bot:
Expose search metrics to Javascript for performance tooling

https://gerrit.wikimedia.org/r/119503
Comment 11 Gerrit Notification Bot 2014-03-21 23:13:46 UTC
Change 119505 merged by jenkins-bot:
Remove completely useless implementation of getInfo()

https://gerrit.wikimedia.org/r/119505
Comment 12 Chad H. 2014-03-23 02:28:34 UTC
We now embed start time & end time (unix timestamp in ms) as well as the time spent in Elasticsearch (in ms). Closing as fixed as I think this is enough for now. If we need further metrics just file a new bug or reopen this one.

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


Navigation
Links