Perfomatic:UI: Difference between revisions
Jump to navigation
Jump to search
(feedback from sayre) |
(one down, one new) |
||
| Line 26: | Line 26: | ||
*** export CSV - server broken | *** export CSV - server broken | ||
*** link - needs url shortener | *** link - needs url shortener | ||
*** embed - not implemented | *** embed - not implemented | ||
** set selection range based on URL | |||
** add test data -> | ** add test data -> | ||
*** put popular branches/tests/platforms on top | *** put popular branches/tests/platforms on top | ||
* plot | * plot | ||
** y-axis should always be 0-based | ** <strike>y-axis should always be 0-based</strike> | ||
== Performance optimizations == | == Performance optimizations == | ||
Revision as of 23:42, 17 December 2010
Design
Designed by Chris Howse
Implementation
Missing features from current design
- dashboard ->
- toolbar ->
- product - not implemented
- platforms - not implemented
- top tests - not implemented
- data grid ->
- row/column should not scroll
- toolbar ->
- 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
- toolbar ->
- plot
y-axis should always be 0-based
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)
- or do it in the app
- improve charting performance
- "double-buffering" canvas for flot
- stack overflow discussion
- custom chart is much faster if each series is written to a hidden canvas then shown when they are all complete
- look into reducing number of points
- flot plots way more than is actually useful when graphs are very dense, flot group discussion
- look into flot alternatives
- "double-buffering" canvas for flot
Testing
- stand up vhost with old graphserver, pointing at nightly database, for QA comparison
- set up lint and tests on Hudson
- 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