Comment #3 on issue 859 by mikhail.naganov: Cleanup: remove log compression and memory buffer logging. It is no more used in Chrome.
http://code.google.com/p/v8/issues/detail?id=859
Danny, I have looked at your inspector for nodeJS. I must say, this is pretty cool! However, I think that relying on the log is not a desired way to go. Here is why:
- first, memory buffer used for log is of a limited size (50M); I introduced a simple compression scheme for CPU profiler records, which provides good utilization for this space, but, at some point in time, profiling will just stop. This was considered OK for profiling web apps, but may be a problem for server apps running for a long time;
- second, memory buffer approach was considered by me as temporary (yes, there is no other long lasting solutions like temporary ones, but still), and recently I reworked profiler API to match WebKit JSC API, so lots of code in WebKit can be used both for JSC and V8; so, I will not be adding any more features to the log, and, even more, I intend to remove memory logging to clean up code in V8, which is currently unnecessary complicated;
Right now, all the new interface is in 'v8-profiler.h' header. A problem that you will encounter is how to allow remote access to this API. In WebKit / Chrome we use bindings that allow us to serialize requests and data into JSON and pass it over the wire to Inspector.
For heap snapshots, you have an even better alternative. Recently I implemented serialization of heap snapshots into JSON on V8's side. And my intention is to use this API for Inspector, so it is here to stay.
Please let me now what do you think about this. -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev
