Closed Bug 1251353 Opened 8 years ago Closed 8 years ago

Add a basic dashboard comparing e10s vs. non-e10s performance on mozilla-inbound

Categories

(Tree Management :: Perfherder, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: wlach, Assigned: wlach)

References

Details

Attachments

(1 file)

We want this for tracking e10s performance. To keep things reasonable and up to date, we'll generate the numbers by getting the values over the last two days on the configuration closest to release (pgo). This will mean that there will be some latency between people checking in fixes/regressions and us noticing on the dashboard, but we have regular old perfherder alerts for that.
Comment on attachment 8723711 [details] [review]
[treeherder] wlach:1251353 > mozilla:master

The e10s-dashboard is more or less designed as throwaway code, but let me know if you have any feedback.
Attachment #8723711 - Flags: review?(jmaher)
Comment on attachment 8723711 [details] [review]
[treeherder] wlach:1251353 > mozilla:master

looking good- lots of changes and good refactoring for reusing a lot of the compare code.
Attachment #8723711 - Flags: review?(jmaher) → review+
Keywords: autoland
Keywords: autoland
Commits pushed to master at https://github.com/mozilla/treeherder

https://github.com/mozilla/treeherder/commit/fdb4b841ebbaa763f6ee1527215dacc3fdf15ff8
Bug 1251353 - Put filtering options directly into compare table

This gives us the filtering view for free on all comparison
views (e.g. compare subtest, compare e10s-vs-non-e10s),
whereas previously we only had it on the main comparison view

https://github.com/mozilla/treeherder/commit/47ac44c2e1cc4c7c5ef6832886f55a3deccf0b7d
Bug 1251353 - Add a dashboard for tracking e10s vs. non-e10s performance
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Commit pushed to master at https://github.com/mozilla/treeherder

https://github.com/mozilla/treeherder/commit/75261b794ff761fba55d4cfddbd0a191acb02254
Bug 1251353 - Fix persistence of filter settings

We would take the correct parameters from the URL, but the actual
filter form fields would not reflect it.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: