Status: Accepted Owner: mikhail.naganov Labels: Type-Bug Priority-High
New issue 714 by mikhail.naganov: CPU profiler [new version]: handling of code events isn't scalable
http://code.google.com/p/v8/issues/detail?id=714 http://code.google.com/p/chromium/issues/detail?id=16184 contains a page 'lots-of-iframes-js.html' which slows down 10-15 times (20 times according to problem explorer) when running under the CPU profiler. While investigating the issue, I found that slowdown happens due to a massive stream of code events produced while executing page's code in Chromium -- the rate is 100K events per second (probably due to intensive iframes creation). The current implementation just can't handle this event rate in a timely manner, resulting in VM slowdown. I already found a solution that works, and having it in place, page's execution time is similar to the case when profiler is disabled. Just need to brush it up and will submit. -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
