ca196b7bb9
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}
39 lines
988 B
JSON
39 lines
988 B
JSON
{
|
|
"name": "Memory",
|
|
"run_count": 5,
|
|
"units": "bytes",
|
|
"path" : ["."],
|
|
"binary": "cctest",
|
|
"main": "test-serialize/SerializationMemoryStats",
|
|
"tests": [
|
|
{
|
|
"name": "ReservedMemoryIsolate",
|
|
"results_regexp": "(\\d+) bytes per isolate$"
|
|
},
|
|
{
|
|
"name": "ReservedMemoryContext",
|
|
"results_regexp": "(\\d+) bytes per context #0$"
|
|
},
|
|
{
|
|
"name": "SnapshotSizeStartup",
|
|
"results_regexp": "(\\d+) bytes for startup$"
|
|
},
|
|
{
|
|
"name": "SnapshotSizeBuiltins",
|
|
"results_regexp": "(\\d+) bytes for builtins$"
|
|
},
|
|
{
|
|
"name": "SnapshotSizeContext",
|
|
"results_regexp": "(\\d+) bytes for context #0$"
|
|
},
|
|
{
|
|
"name": "DeserializationTimeIsolate",
|
|
"results_regexp": "\\[Deserializing isolate \\(\\d+ bytes\\) took ([\\d.]+) ms\\]"
|
|
},
|
|
{
|
|
"name": "DeserializationTimeContext",
|
|
"results_regexp": "\\[Deserializing context #0 \\(\\d+ bytes\\) took ([\\d.]+) ms\\]"
|
|
}
|
|
]
|
|
}
|