VV8 LUCI CQ[snapshot] Add RO deserialization time graph
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[snapshot] Add RO deserialization time graph .. and split it out from the isolate deserialization time graph. Previously, the DeserializationTimeIsolate metric measured everything inside Isolate::Init, i.e. RO deserialization, isolate deserialization, and various isolate setup code. With this change, DeserializationTimeIsolate measures only isolate deserialization, and DeserializationTimeReadOnly measures only RO space deserialization. Bug: v8:13789 Change-Id: I83762fa34b46c8cd6819f309f845b6b0dcedcde8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4840339 Auto-Submit: Jakob Linke <jgruber@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#89808} | 2 年前 | |
[perf] Refactor the Memory benchmark to use d8 Until this CL, the Memory benchmark was the only one to be based on a cctest runner; all others use d8. Besides being a tedious exception to the rule, this caused issues such as described in the linked bug (summary: refbuilds are built with v8_static_library, and neither cctests nor unittests support this configuration). Here, we move the Memory benchmark into a d8 runner. Bug: v8:9189, chromium:957029 Change-Id: I9b45ff36f4842cb0bdef2c1c4b0184c5509d3385 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1588464 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by: Sigurd Schneider <sigurds@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Sergiy Belozorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#61245} | 7 年前 |