Firefox/Goals/2010Q1/IO Reduction Criteria: Difference between revisions

From MozillaWiki
< Firefox‎ | Goals‎ | 2010Q1
Jump to navigation Jump to search
mNo edit summary
(Added links to endpoint log and changeset it was built off of.)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
This is the current criteria used for the goal "> 50% reduction of main thread I/O".  This may not be the best criteria out there, but it's the best we've got at the moment.  This may improve over time.
This is the current criteria used for the goal "> 50% reduction of main thread I/O".  This may not be the best criteria out there, but it's the best we've got at the moment.  This may improve over time.


[http://files.shawnwilsher.com/2010/1/8/data.log Starting point log] from a build off of [http://hg.mozilla.org/mozilla-central/rev/5fdbc534a253 changeset 5fdbc534a253].
[http://files.shawnwilsher.com/2010/3/9/data.log Starting point log] from a build off of [http://hg.mozilla.org/mozilla-central/rev/3e80559aea9e changeset 3e80559aea9e].
 
[http://files.shawnwilsher.com/2010/4/6/data.log End point log] from a build off of [http://hg.mozilla.org/mozilla-central/rev/4f440b68d7b1 changeset 4f440b68d7b1]


The numbers are obtained with [[Firefox/Goals/2010Q1/IO Reduction Criteria/sdwilsh-io.d|this DTrace script]].
The numbers are obtained with [[Firefox/Goals/2010Q1/IO Reduction Criteria/sdwilsh-io.d|this DTrace script]].


Steps to run for version 1.1:<pre>
Steps to run for version 1.2:<pre>
new profile, open once, let it do its normal first run thing.
new profile, open once, let it do its normal first run thing.
clear history.
clear history.
Line 19: Line 21:
wait for page to load; cmd + l; facebook.com
wait for page to load; cmd + l; facebook.com
wait for page to load; log in to facebook
wait for page to load; log in to facebook
wait for page to load; techcrunch.com
wait for page to load; cmd + l; cnn.com
wait for page to load; cmd + l; google.com
wait for page to load; cmd + l; gmail.com
wait for page to load (+inbox fully loaded); cmd + l; digg.com
wait for page to load; cmd + l; twitter.com
wait for page to load; cmd + l; facebook.com
wait for page to load; techcrunch.com
wait for page to load; techcrunch.com
wait for page to load; cmd + l; cnn.com
wait for page to load; cmd + l; cnn.com
wait for page to load; quit
wait for page to load; quit
stop dtrace script</pre>
stop dtrace script</pre>

Latest revision as of 21:59, 6 April 2010

This is the current criteria used for the goal "> 50% reduction of main thread I/O". This may not be the best criteria out there, but it's the best we've got at the moment. This may improve over time.

Starting point log from a build off of changeset 3e80559aea9e.

End point log from a build off of changeset 4f440b68d7b1

The numbers are obtained with this DTrace script.

Steps to run for version 1.2:

new profile, open once, let it do its normal first run thing.
clear history.
open up one more time, then quit.
dtrace -s sdwilsh-io.d > data.log
./firefox-bin -P io
wait for page to load; cmd + l; google.com
wait for page to load; cmd + l; gmail.com
wait for page to load; login to gmail
wait for page to load (+inbox fully loaded); cmd + l; digg.com
wait for page to load; cmd + l; twitter.com
wait for page to load; log in to twitter
wait for page to load; cmd + l; facebook.com
wait for page to load; log in to facebook
wait for page to load; techcrunch.com
wait for page to load; cmd + l; cnn.com
wait for page to load; cmd + l; google.com
wait for page to load; cmd + l; gmail.com
wait for page to load (+inbox fully loaded); cmd + l; digg.com
wait for page to load; cmd + l; twitter.com
wait for page to load; cmd + l; facebook.com
wait for page to load; techcrunch.com
wait for page to load; cmd + l; cnn.com
wait for page to load; quit
stop dtrace script