Bug 77364
| Summary: | Performance tests should let garbage collection happen at an arbitrary time and report the GC time separately | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ryosuke Niwa <rniwa> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | abarth, andersca, eric, leviw, morrita, oliver |
| Priority: | P3 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 77037 | ||
Ryosuke Niwa
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ryosuke Niwa
This is a nice-to-have feature but I wouldn't prioritize it at the moment.
Hajime Morrita
(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.