search

uppet / speedtracer

Automatically exported from code.google.com/p/speedtracer
1 stars 0 forks source link

Distinguish Garbage Collections #32

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What feature are you requesting?

V8 has a number of different garbage collection types (scavenge, 
non-compacting, full compacting), each with different performance 
characteristics.  Is it possible for Speed Tracer to distinguish between these 
types of collections?

What benefits would the feature provide?

When building large javascript applications, it would be nice to have a closer 
look into when the garbage collector is running which type of collection.  
There could be significant gains to be had if you could find and optimize the 
spots in your code where you're putting a lot of stress on the memory 
management system.

I have no idea if you're instrumenting into V8, or if V8 exposes this kind of 
information to Chrome when it garbage collects, but if the information is 
available, it'd be nice to see this distinguished on those events.

Original issue reported on code.google.com by JayYoung...@gmail.com on 28 Nov 2010 at 10:03

GoogleCodeExporter commented 9 years ago

Original comment by knor...@google.com on 21 Jun 2011 at 7:23