398327 - Can't get per-page performance data out of graph server

Status: RESOLVED DUPLICATE of bug 438716

(Webtools Graveyard :: Graph Server, defect, P3)

Description

[Boris Zbarsky [:bzbarsky]]

BUILD:  Current trunk

STEPS TO REPRODUCE:
1)  Disable the slow script dialog.
2)  Load http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox
3)  Click the "tp_l_1" link on a cycle of "WINNT 5.1 talos trunk qm-pxp01"
4)  Wait a few minutes (I waited 3 minutes or so) during which the browser
    consumes 100% CPU and is unresponsive.
5)  Start profiler
6)  Profile for a bit
7)  Stop profiler
8)  Kill the unresponsive browser

ADDITIONAL INFORMATION: All the time is spent under the load completion of an XMLHttpRequest, executing JS.  About 1/8 of the total time is spent in security checks during said JS execution, and a small amount spent on changing attributes on <options>, but most of the time is JS execution itself.

This makes it impossible to get per-page numbers that would be needed in debugging a Tp regression.

Comment 1

[[e-mail] (:bhearsum)]

This WFM on the latest Minefield. The browser is unresponsive for a short period of time after the page loads (presumably while the graph data is being retrieved), and then displays the graph.

Comment 2

[alice nodelman [:alice] [:anode]]

It's true that it is hard to get the per page data out of the graph server without timeouts/freeze up in the browser, but this should go away with vlad's work on a new graph server front end.