Electrolysis/Release Criteria/Jank: Difference between revisions

Electrolysis/Release Criteria/Jank (view source)

694 bytes added , 23 February 2016

→‎Talos tp5o_responsiveness: results of yesterday's investigations.

106

edits

@@ Line 52: / Line 52: @@
 This test is hugely better in e10s. tp5o_responsiveness on WinXP mozilla-central (results not available on Aurora).
-Concerns: Is this number valid? Why is it so much better in e10s? Is it from the chrome process or content?
+Contact points for this test are listed in its [https://wiki.mozilla.org/Buildbot/Talos/Tests#Responsiveness|Talos Test Description]. At time of edit, these are :jimm and :jmaher.
-A RESPONSIBLE PARTY NEEDS TO BE FOUND FOR THIS TEST
+On consulting the relevant bug ({{bug|710296}}), :avih and :jmaher, and the test's bug ({{bug|631571}}) I learned that the test results should be expected. The test does the following: while loading the tp5 top websites, inject custom tracer events into the parent process' event loop and measure how long it takes for them to percolate through.
+This test is a valid test of chrome responsiveness during content load. Chrome responsiveness under heavy content load is expected to improve (that being one of the reasons for E10s in the first place).
+'''next steps''': PASS (pending :avih's validation and documentation of tp5o_responsiveness' usefulness as an e10s metric)
 === GC pauses ===