Bug 77364 - Performance tests should let garbage collection happen at an arbitrary time and report the GC time separately
Summary: Performance tests should let garbage collection happen at an arbitrary time a...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P3 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 77037
  Show dependency tree / graph
 
Reported: 2012-01-30 13:17 PST by Ryosuke Niwa
Modified: 2012-02-01 17:42 PST (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ryosuke Niwa 2012-01-30 13:17:19 PST 
After http://trac.webkit.org/changeset/106211, we force gc() after each test run. However, we should also have a way to measure the time we spend in garbage collection and report it separately. e.g. if we some changeset make us spend 1000ms in gc instead of 100ms, then performance tests should capture that.
Comment 1 Ryosuke Niwa 2012-01-30 13:20:38 PST 
This is a nice-to-have feature but I wouldn't prioritize it at the moment.
Comment 2 Hajime Morrita 2012-02-01 17:42:07 PST 
(In reply to comment #1)
> This is a nice-to-have feature but I wouldn't prioritize it at the moment.
And it makes less sense for modern VMs which has generational/incremental GC.
V8 has it. And JSC also has or is going to have one.

What we need is, IMO, the profiler dump for each (or part of) test run.