Closed
Bug 601796
Opened 14 years ago
Closed 13 years ago
implement new graphserver front-end design
Categories
(Webtools Graveyard :: Graph Server, defect, P2)
Webtools Graveyard
Graph Server
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rhelmer, Assigned: rhelmer)
References
()
Details
Attachments
(4 files)
chowse has designed a most excellent new front-end for graphserver (see attachments and URL). This should (hopefully!) require few changes on the server-side, I'm investigating this now.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → robert
Assignee | ||
Comment 1•14 years ago
|
||
Assignee | ||
Comment 2•14 years ago
|
||
Assignee | ||
Comment 3•14 years ago
|
||
Assignee | ||
Comment 4•14 years ago
|
||
Comment 5•14 years ago
|
||
You should also keep in mind that we store the individual results for each test (ie, for ts we have all 20 browser startups and for tp we have all the individual page load times). It would be nice to be able to drill down into a graph to see this detail. There have also been requests to be able to compare individual page load times in each test over time, so say I want to monitor to see if the 80th page in tp has individually regressed over time - we currently have no way of doing this.
Comment 6•14 years ago
|
||
(In reply to comment #5) > You should also keep in mind that we store the individual results for each test > (ie, for ts we have all 20 browser startups and for tp we have all the > individual page load times). It would be nice to be able to drill down into a > graph to see this detail. This design does support this, to a degree. In attachment 480791 [details], you have the option of selecting individual pages if the user selects Tp or Ts. I didn't mock-up how this would be displayed in the legend, but it would probably be no more complex than adding an extra line w/ the chosen page. Alternately, we could support a second way of 'exploding' a data series: instead of splitting it up by machine, we could split it up by sub-test, e.g. page or startup. This would take a bit more effort to design, but if there's a strong case for seeing the results of EVERY sub-test (rather than a select few), I can find a way to add it.
Assignee | ||
Updated•14 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 7•14 years ago
|
||
Latest work is staged: http://graphs-stage2.mozilla.org Currently working through missing features and perf optimizations: https://wiki.mozilla.org/Perfomatic:UI#Missing_features_from_current_design As soon as we're through that list, we're going to: 1) create a 2.0 branch hg.m.o/graphs and push latest 2) install 2.0 to graphs-new.m.o (alongside current 1.0 on graphs.m.o) Feel free to drop into #perfomatic if you have any questions/concerns in the meantime.
Assignee | ||
Updated•13 years ago
|
Priority: -- → P2
Assignee | ||
Comment 8•13 years ago
|
||
Production server is up: http://graphs-new.mozilla.org We'll start advertising it on the old server once it's had some field testing, and eventually will take over the http://graphs.mozilla.org URL. Further bugfixes and enhancements will be carried out in individual bugs. Thanks to everyone who made this happen!
Assignee | ||
Updated•13 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•