v8/test/memory/Memory.json
Jakob Gruber 226b58341e [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}
2019-05-06 15:10:57 +00:00

45 lines
1.2 KiB
JSON

{
"owners": ["yangguo@chromium.org", "jgruber@chromium.org"],
"name": "Memory",
"run_count": 5,
"units": "bytes",
"resources": ["run.js"],
"main": "run.js",
"path": ["."],
"flags": ["--allow-natives-syntax", "--profile-deserialization"],
"tests": [
{
"name": "ReservedMemoryIsolate",
"results_regexp": "(\\d+) bytes per isolate$"
},
{
"name": "ReservedMemoryContext",
"results_regexp": "(\\d+) bytes per context #0$"
},
{
"name": "SnapshotSizeStartup",
"results_regexp": "(\\d+) bytes in \\d+ chunks for startup$"
},
{
"name": "SnapshotSizeReadOnly",
"results_regexp": "(\\d+) bytes for read-only$"
},
{
"name": "SnapshotSizeContext",
"results_regexp": "(\\d+) bytes in \\d+ chunks 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\\]"
},
{
"name": "EmbeddedBuiltinsSize",
"results_regexp": "^Embedded blob is (\\d+) bytes$"
}
]
}