Auto-tools/Projects/XTalos: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(15 intermediate revisions by one other user not shown)
Line 18: Line 18:
== Team ==
== Team ==


* '''Feature Manager''': ''jmaher''
* '''Talos Developer''': jmaher
* '''Lead Developer''': jmaher, taras, sdwilsh
* '''Platform Developer''': taras, sdwilsh
* '''Talos Advisor''': anode
* '''Talos Advisor''': anode


== Release Requirements ==
== Release Requirements ==


* turn on xperf for talos tests  
* turn on xperf (windows 7) for talos ts and tp4 tests
* replace cpu,memory,private bytes, etc.. with xperf (windows 7) collection
* modify pageloader to load pages with keypress or link clicking
* modify pageloader to load pages with keypress or link clicking
** for tp4 (initially)


== Next Steps ==
== Next Steps ==
* get .etl file scraper for existing xperf tests
* get .etl file scraper for existing xperf tests [[https://bitbucket.org/jmaher/xtalos/src/82c01292752f/etlparser.py etlparser.py]]
* start review process of xperf patch for talos
* start review process of xperf patch for talos {{bug|609111}}
* make decisions on future xperf usage (replace current counter collection)
* make decisions on future xperf usage (replace current counter collection)
* make decisions on realistic tests to run this on
* make decisions on realistic tests to run this on
Line 35: Line 37:


== Open Issues ==
== Open Issues ==
Unanswered questions, things that need to be explored, decisions that still need to be made, etc.
* what data to parse out of .etl file
** # files accessed during startup
** list of files accessed during tp on main thread
* how to upload .etl files from talos test slaves
* where to put .etl files for referencing
* where/how to upload the test results we generate


== Related Bugs & Dependencies ==
== Related Bugs & Dependencies ==
Links to the feature tracking bug & other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.
* {{bug|609111}} - passed prototype stage, preparing releng machines, need to start reviews.
 
== Designs =={| class="fullwidth-table"
|-
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD;" | Status
| style="font-weight: bold; background: #DDD;" | ETA
| style="font-weight: bold; background: #DDD;" | Owner
|-
<section begin="status" />
| [[Feature Page Structure]]
| {{StatusHealthy|status=One or two sentence status report.}}
| YYYY-MM-DD
| Owner Name
<section end="status" />
|-
|}
 
== Summary ==
Very succinct (one or two line) summary of what this feature is all about.
 
== Team ==
Who's working on this?
 
* '''Feature Manager''': ''(required)''
* '''Lead Developer''':
* '''Product Manager''':
* '''QA''':
* '''UX''':
* '''Security''':
* Etc.
 
Team list should make it clear who to ask about what, and who to ping when they're needed.  If you do not need someone in a particular role (ie: Security), that's fine, just delete that line.
 
== Release Requirements ==
Complete checklist of items that need to be satisfied before we can call this feature "done". 
 
== Next Steps ==
Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished.
 
== Open Issues ==
Unanswered questions, things that need to be explored, decisions that still need to be made, etc.
 
== Related Bugs & Dependencies ==
Links to the feature tracking bug & other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.
 
== Designs ==
Any and all mockups, design specs, tech specs, etc.  Either inline or linked to.
 
== Test Plans ==
Any and all test plans and strategies.  Either inline or linked to.
 
== Goals/Use Cases ==
The high level goals for the feature (which the release requirements checklist should fulfill).  These are the guiding light and overall vision for the feature.  Refer to this if there is confusion or are disputes about direction, designs, planning, etc.
 
== Non-Goals ==
Things we are specifically not doing or building as part of this feature.
 
== Other Documentation ==
Can include things like:
* Competitive landscape
* Research & references
* Whatever else is useful to the project.
 
== Legend (remove if you like) ==
{| class="fullwidth-table"
|-
| {{StatusHealthy|status=&nbsp;}}
| Healthy: feature is progressing as expected.
|-
| {{StatusBlocked|status=&nbsp;}}
| Blocked: feature is currently blocked.
|-
| {{StatusAtRisk|status=&nbsp;}}
| At Risk: feature is at risk of missing its targeted release.
|-
| '''ETA'''
| Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.
|}
 
__NOTOC__
 
Please remove this line and any non-relevant categories below.  Add whatever other categories you feel are appropriate.
 
[[Category:Features]]
[[Category:Firefox]]
[[Category:Performance]]
[[Category:Polish]]
[[Category:Priority 1]]
[[Category:Priority 2]]
[[Category:Priority 3]]
[[Category:Unprioritized]]
 
Any and all mockups, design specs, tech specs, etc.  Either inline or linked to.
 
== Test Plans ==
Any and all test plans and strategies.  Either inline or linked to.


== Goals/Use Cases ==
== Goals/Use Cases ==
The high level goals for the feature (which the release requirements checklist should fulfill).  These are the guiding light and overall vision for the feature.  Refer to this if there is confusion or are disputes about direction, designs, planning, etc.
== Non-Goals ==
Things we are specifically not doing or building as part of this feature.
== Other Documentation ==
Can include things like:
* Competitive landscape
* Research & references
* Whatever else is useful to the project.
== Legend (remove if you like) ==
{| class="fullwidth-table"
|-
| {{StatusHealthy|status=&nbsp;}}
| Healthy: feature is progressing as expected.
|-
| {{StatusBlocked|status=&nbsp;}}
| Blocked: feature is currently blocked.
|-
| {{StatusAtRisk|status=&nbsp;}}
| At Risk: feature is at risk of missing its targeted release.
|-
| '''ETA'''
| Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.
|}
__NOTOC__
Please remove this line and any non-relevant categories below.  Add whatever other categories you feel are appropriate.
[[Category:Features]]
[[Category:Firefox]]
[[Category:Performance]]
[[Category:Polish]]
[[Category:Priority 1]]
[[Category:Priority 2]]
[[Category:Priority 3]]
[[Category:Unprioritized]]
|}
== Summary ==
Very succinct (one or two line) summary of what this feature is all about.
== Team ==
Who's working on this?
* '''Feature Manager''': ''(required)''
* '''Lead Developer''':
* '''Product Manager''':
* '''QA''':
* '''UX''':
* '''Security''':
* Etc.
Team list should make it clear who to ask about what, and who to ping when they're needed.  If you do not need someone in a particular role (ie: Security), that's fine, just delete that line.
== Release Requirements ==
Complete checklist of items that need to be satisfied before we can call this feature "done". 
== Next Steps ==
Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished.
== Open Issues ==
Unanswered questions, things that need to be explored, decisions that still need to be made, etc.
== Related Bugs & Dependencies ==
Links to the feature tracking bug & other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.


== Designs ==
* provide useful non time based performance data to improve Firefox performance on Windows
Any and all mockups, design specs, tech specs, etc.  Either inline or linked to.
 
== Test Plans ==
Any and all test plans and strategies.  Either inline or linked to.
 
== Goals/Use Cases ==
The high level goals for the feature (which the release requirements checklist should fulfill).  These are the guiding light and overall vision for the feature.  Refer to this if there is confusion or are disputes about direction, designs, planning, etc.


== Non-Goals ==
== Non-Goals ==
Things we are specifically not doing or building as part of this feature.
* rewriting talos for mac/linux.
* measuring user use cases (like clicking on menu's, bookmarks, etc...)


== Other Documentation ==
== Other Documentation ==
Can include things like:
* Competitive landscape
* Research & references
* Whatever else is useful to the project.


== Legend (remove if you like) ==
* repository for [[https://bitbucket.org/jmaher/xtalos xperf toolchain]]
{| class="fullwidth-table"
* TODO: include links to xperf and related stuff
|-
| {{StatusHealthy|status=&nbsp;}}
| Healthy: feature is progressing as expected.
|-
| {{StatusBlocked|status=&nbsp;}}
| Blocked: feature is currently blocked.
|-
| {{StatusAtRisk|status=&nbsp;}}
| At Risk: feature is at risk of missing its targeted release.
|-
| '''ETA'''
| Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.
|}


__NOTOC__
__NOTOC__


Please remove this line and any non-relevant categories below.  Add whatever other categories you feel are appropriate.
[[Category:Features]]
[[Category:Firefox]]
[[Category:Firefox]]
[[Category:Performance]]
[[Category:Polish]]
[[Category:Priority 1]]
[[Category:Priority 2]]
[[Category:Priority 3]]
[[Category:Unprioritized]]

Latest revision as of 23:19, 27 June 2015

Feature Status ETA Owner
Windows Performance Testing (xperf, talos, pageloader) Continuing Effort, and new planning. 2011-06-15 Joel Maher

Summary

Integrate talos testing to measure with xperf and provide various page load techniques to measure code paths our users normally do.

Team

  • Talos Developer: jmaher
  • Platform Developer: taras, sdwilsh
  • Talos Advisor: anode

Release Requirements

  • turn on xperf (windows 7) for talos ts and tp4 tests
  • replace cpu,memory,private bytes, etc.. with xperf (windows 7) collection
  • modify pageloader to load pages with keypress or link clicking
    • for tp4 (initially)

Next Steps

  • get .etl file scraper for existing xperf tests [etlparser.py]
  • start review process of xperf patch for talos bug 609111
  • make decisions on future xperf usage (replace current counter collection)
  • make decisions on realistic tests to run this on
  • make decisions on pageloader modifications

Open Issues

  • what data to parse out of .etl file
    • # files accessed during startup
    • list of files accessed during tp on main thread
  • how to upload .etl files from talos test slaves
  • where to put .etl files for referencing
  • where/how to upload the test results we generate

Related Bugs & Dependencies

  • bug 609111 - passed prototype stage, preparing releng machines, need to start reviews.

Goals/Use Cases

  • provide useful non time based performance data to improve Firefox performance on Windows

Non-Goals

  • rewriting talos for mac/linux.
  • measuring user use cases (like clicking on menu's, bookmarks, etc...)

Other Documentation

  • repository for [xperf toolchain]
  • TODO: include links to xperf and related stuff