46714 - need bloatblame graphical FE (stripchart)

Status: RESOLVED INCOMPLETE

(Core :: XPCOM, defect, P3)

Description

[Warren Harris]

10) Bloatblame FE
  Description: Currently bloatblame is a post-processing tool. We believe we can 
get much more useful information if we can get 
  more real-time data of module memory usage. Brendan has been working on the 
back-end of the real-time bloatblame. Wade 
  and Pavlov are both looking into a front-end to display/graph the data.
  Module owner: [e-mail]
  Task owner: [e-mail], [e-mail]
  Status: Brendan is on vacation and we believe that the currently checked in 
version does not implement all the back-end 
  changes necessary. We may need to wait till Brendan returns.


I see that Brendan checked in tmreader (xpcom/base/tmreader.c) which is the 
backend to the bloatblame tool. The stripchart utility that Wade came up with 
should be hooked up to that.

Comment 1

[Peter Trudelle]

nsbeta3-, there is no way we would hold NS6 until we get a graphical front end
on a bloat utility.  

Comment 2

[Warren Harris]

This is essential for the analysis phase of the footprint work. We need to get 
the people closest to the code looking at their memory consumption. I've 
already met with pdt to ok this process. This is essential for embedding, and 
highly desirable for seamonkey. nsbeta3+

Comment 3

[Peter Trudelle]

Okay, but we don't have time to do it for you for nsbeta3.  Pav says Wade
already looked at this, you might try him.  In the meantime, reassigning to you.

Comment 4

[Warren Harris]

Reassigning to wade.

Comment 5

[Brendan Eich [:brendan]]

Pavlov has spent some time looking at alternatives and thinking about this.

My bloatstrip/bloatblame changes have yet to land, in part because I'm working 
on bugs that even warren would say are more important (bug 46703 to name one).  
Wade, if you are hacking on stuff, please let us know here so we can coordinate.

/be

Comment 6

[Warren Harris]

Forth week with no activity -- marking nsbeta3-.

Comment 7

[chris hofmann]

steve, sommething to think about.

Comment 8

[Thomas]

Anyone familiar with bloatblame?

Comment 9

[Brendan Eich [:brendan]]

Probably a new bug should be filed. Thought I'd cc: a few folks interested in a real-time cheap/coarse memory profiler.

/be