Perfomatic:UI: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(tools)
(linewidth)
Line 45: Line 45:
* <strike>add caching proxy (varnish, etc)</strike>
* <strike>add caching proxy (varnish, etc)</strike>
* improve charting performance  
* improve charting performance  
** forcing lineWidth to 1 seems to make a huge difference
*** started [https://groups.google.com/forum/#!topic/flot-graphs/tJDCYMe-0Nw discussion on the flot list]
*** however does not look as good, not pushing to stage until further investigation
** "double-buffering" canvas for flot
** "double-buffering" canvas for flot
*** [http://stackoverflow.com/questions/2795269/does-html5-canvas-support-double-buffering/2864533#2864533 stack overflow discussion]
*** [http://stackoverflow.com/questions/2795269/does-html5-canvas-support-double-buffering/2864533#2864533 stack overflow discussion]

Revision as of 19:38, 1 January 2011

Design

Designed by Chris Howse

Implementation

Missing features from current design

  • dashboard ->
    • toolbar ->
      • product - not implemented
      • platforms - not implemented
      • top tests - not implemented
      • set pulldowns based on URL
    • data grid ->
      • row/column should not scroll
  • custom chart ->
    • toolbar ->
      • running time - time delta/time delta % not implemented
      • show changesets - needs design work
        • may need hgpushlog work to link directly to changesets
      • export CSV - server broken
      • link - needs url shortener
      • embed - not implemented
    • set selection range based on URL
    • add test data ->
      • put popular branches/tests/platforms on top
  • plot ->
    • y-axis should always be 0-based
  • need mapping between branches and hg repos

Performance optimizations

  • split up JSON files as discussed in status meeting
    • look into constraining by date range
  • set Last-Modified headers on all JSON feeds
    • especially the manifest!
    • already setting 15m Expires/Cache-control max-age
  • add caching proxy (varnish, etc)
  • improve charting performance

Testing

  • stand up vhost with old graphserver, pointing at nightly database, for QA comparison
  • set up lint and tests on Hudson
    • selenium tests (in progress)
      • show these to QA to run on their Hudson
    • qUnit/env.js unit tests for JS code
  • stand up auto-update for code (5 minutes) and DB (nightly)
  • (QA) compare actual submitted data to JSON, and confirm in interface
  • make sure proper changeset range is shown for checkins
    • check with catlee on how the tree-management script does this
    • follow-up irc convo w/ ted on catlee on changesets coalescing