Mobile Perf and Responsiveness: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Goals  =
= Goals  =


== Engineering <br> ==
Click the above to see the mobile perf "feature" page that helped spark the conversation. This captures where we were a mere month ago and represents the baseline plan. In summary need to work on:
Land on what architecture we want to use: do we stay with dual architecture or do we move to a single, multi-threaded process?
Status: dougt is working on a build using the Java front-end for testing and evaluation by 10/7.
2. Improve startup time
Status: Java architecture helps us with this but we need to continue to plow through mobile startup shrink bugs.
3. Understand Memory Usage
Status: Pending, more info due by 10/7
4. Improve Perceived Performance
Status: Pending, more info due by 10/7
5. Improve Page Load, Panning, Zooming
Status: Pending more info due by 10/7
== Big Picture<br> ==
== Big Picture<br> ==


Line 9: Line 32:
* Be faster and better than iOS Browsers<br>
* Be faster and better than iOS Browsers<br>


== Testing &amp;&nbsp;Benchmarking<br> ==
== Testing &amp;&nbsp;Benchmarking<br> ==
 
*Scale our current automated performance testing and benchmarking infrastructure so that it supports continued innovation and yields reliable data for engineering and quality assurance
*'''Status:&nbsp;'''Currently focusing on the reliability of Unit and Talos testing; we will then move onto adding new tests such as RSS. Dates to track incremental progress again is forthcoming.
 
*Create standards of testing, measurement, and analysis to provide a concrete view into how Fennec performs to complement the above benchmarks to be then leveraged for ongoing crowdsource testing:
*'''Status:&nbsp;'''We have an "approved"&nbsp;matrix of test cases and metrics we will collect. Methodology for testing and analysis due on 10/4. Aaron Train is doing a QA&nbsp;test day on 10/7. We will iterate on this process and design a way to crowdsource this testing by the end of the year.


== [https://wiki.mozilla.org/Features/MobilePerformance Engineering]  ==
*Scale our current automated performance testing and benchmarking infrastructure so that it supports continued innovation and yields reliable data for engineering and quality assurance<br>
*'''Status:&nbsp;'''Currently focusing on the reliability of Unit and Talos testing; we will then move onto adding new tests such as RSS. Dates to track incremental progress again is forthcoming.


Click the above to see the mobile perf "feature"&nbsp;page that helped spark the conversation. This captures where we were a mere month ago and represents the baseline plan. In summary need to work on: <br>
*Create standards of testing, measurement, and analysis to provide a concrete view into how Fennec performs to complement the above benchmarks to be then leveraged for ongoing crowdsource testing:
*'''Status:&nbsp;'''We have an "approved"&nbsp;matrix of test cases and metrics we will collect. Methodology for testing and analysis due on 10/4. Aaron Train is doing a QA&nbsp;test day on 10/7.  
*Integrate with Telemetry
*'''Status:&nbsp;'''Work with telemetry team to integrate metrics to crowdsource results; will hopefully land on a plan during the mobile work week.


* Land on what architecture we want to use: do we stay with dual architecture or do we move to a single, multi-threaded process?
<br>
<br>


* Status:&nbsp;dougt is working on a build using the Java front-end for testing and evaluation by 10/7
<br>

Latest revision as of 17:22, 4 October 2011

Goals

Engineering

Click the above to see the mobile perf "feature" page that helped spark the conversation. This captures where we were a mere month ago and represents the baseline plan. In summary need to work on:

Land on what architecture we want to use: do we stay with dual architecture or do we move to a single, multi-threaded process?

Status: dougt is working on a build using the Java front-end for testing and evaluation by 10/7.

2. Improve startup time

Status: Java architecture helps us with this but we need to continue to plow through mobile startup shrink bugs.

3. Understand Memory Usage

Status: Pending, more info due by 10/7

4. Improve Perceived Performance

Status: Pending, more info due by 10/7

5. Improve Page Load, Panning, Zooming

Status: Pending more info due by 10/7

Big Picture

  • Provide customers with a mobile browser that exceeds customer expectations in terms of responsiveness by March 2012
  •  Be faster than native Android Browsers
  • Be faster and better than iOS Browsers

Testing & Benchmarking

  • Scale our current automated performance testing and benchmarking infrastructure so that it supports continued innovation and yields reliable data for engineering and quality assurance
  • Status: Currently focusing on the reliability of Unit and Talos testing; we will then move onto adding new tests such as RSS. Dates to track incremental progress again is forthcoming.
  • Create standards of testing, measurement, and analysis to provide a concrete view into how Fennec performs to complement the above benchmarks to be then leveraged for ongoing crowdsource testing:
  • Status: We have an "approved" matrix of test cases and metrics we will collect. Methodology for testing and analysis due on 10/4. Aaron Train is doing a QA test day on 10/7.
  • Integrate with Telemetry
  • Status: Work with telemetry team to integrate metrics to crowdsource results; will hopefully land on a plan during the mobile work week.




Retrieved from "https://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=Mobile_Perf_and_Responsiveness&oldid=354714"