talos xperf measures file and network IO, not time- we can run this on any machine. To simplify our requirements moving to new hardware, lets get xperf migrated to a VM.
this is easier than I thought. and earlier try push: https://treeherder.mozilla.org/#/jobs?repo=try&revision=3bcb18f46f9a791702389098f99f8711a57b3172 and a try push with this finalized patch: https://treeherder.mozilla.org/#/jobs?repo=try&revision=45b26bdaa4ee5676984371817fe7c6a626628051
Assignee: nobody → jmaher
Status: NEW → ASSIGNED
Attachment #8933857 - Flags: review?(rwood)
Comment on attachment 8933889 [details] [diff] [review] run xperf on win7-vm instead of hardware LGTM
Attachment #8933889 - Flags: review?(rwood) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/23e1da446559 move talos xperf from win7 hardware to VM. r=rwood
This updated our tp5n nonmain_normal baselines: == Change summary for alert #10867 (as of Mon, 04 Dec 2017 13:11:41 GMT) == Improvements: 48% tp5n nonmain_normal_netio windows7-32 pgo e10s 156,876,812.25 -> 81,215,827.75 47% tp5n nonmain_normal_netio windows7-32 opt e10s 160,984,081.75 -> 84,959,646.50 3% tp5n nonmain_normal_fileio windows7-32 opt e10s 368,390,010.62 -> 356,990,413.82 For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=10867
You need to log in before you can comment on or make changes to this bug.