- 30 Apr, 2019 1 commit
-
-
Mythri A authored
With bytecode flushing and lazy feedback allocation, we need to call %PrepareForOptimization before we call %OptimizeFunctionOnNextCall Bug: v8:8801, v8:8394 Change-Id: I81918f174b2f97cbaa8b8ef2e459080c2581f535 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1588415 Commit-Queue: Mythri Alle <mythria@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#61122}
-
- 18 Mar, 2019 1 commit
-
-
Simon Zünd authored
The serialize set of microbenchmarks serializes Error.stack of a prepared set of error objects. When all objects have been serialized, the benchmark then wrapped around and only accessed the resulting string properties. This, of course, is a lot faster and benchmark results are heavily fluctuating when the end is reached. This CL fixes this by introducing a payload that should be similiar to the specific workload, which is executed after the end is reached. R=petermarshall@chromium.org Bug: v8:8742 Change-Id: I7183d04e7c06af0c16fe3412e902f0d33605bc25 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1524485Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#60297}
-
- 12 Mar, 2019 1 commit
-
-
Simon Zünd authored
This CL adds two sets of benchmarks. The first measures the effort needed to walk the stack and create the data structure stored in Error.stack, while the second measures the serialization of that Error.stack data structure into a string. R=petermarshall@chromium.org, yangguo@chromium.org Bug: v8:8742 Change-Id: Ie7b86da5621cb186a036a3ec99692ec4d2048fba Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1505614 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#60176}
-