Skip to content

Commit ca196b7

Browse files
schuayCommit Bot
authored andcommitted
[snapshot] Track deserialization time in Memory benchmark
test-serialize/SerializationMemoryStats does not actually create a new Isolate from scratch. Instead, it deserializes from the snapshot and we can simply piggy-back off existing output to measure deserialization time. Bug: v8:6666,v8:7693 Change-Id: I8f709ea834ff7f5e46f7ebfa9b0c35d96095bf26 Reviewed-on: https://chromium-review.googlesource.com/1039585 Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#52918}
1 parent aa15b7d commit ca196b7

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

test/memory/Memory.json

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,14 @@
2525
{
2626
"name": "SnapshotSizeContext",
2727
"results_regexp": "(\\d+) bytes for context #0$"
28+
},
29+
{
30+
"name": "DeserializationTimeIsolate",
31+
"results_regexp": "\\[Deserializing isolate \\(\\d+ bytes\\) took ([\\d.]+) ms\\]"
32+
},
33+
{
34+
"name": "DeserializationTimeContext",
35+
"results_regexp": "\\[Deserializing context #0 \\(\\d+ bytes\\) took ([\\d.]+) ms\\]"
2836
}
2937
]
3038
}

0 commit comments

Comments
 (0)