[wasm] Add a counter that compares liftoff with deserialization
- Adds a counter to measure time from creating the async compile job to either baseline compilation or deserialization completion, so we can evaluate the benefit from code caching. - Eliminates the counter that measures deserialization. Bug: chromium:719172 Change-Id: Iefa707ef73ac20377d5164a1bd5f1e462573ce06 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1888829Reviewed-by: Andreas Haas <ahaas@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Bill Budge <bbudge@chromium.org> Cr-Commit-Position: refs/heads/master@{#64694}
Showing
Please
register
or
sign in
to comment