- 24 May, 2019 3 commits
-
-
Simon Zünd authored
This is a reland of 2b0ac2fb The layout test that caused this revert was fixed with: https://crrev.com/c/1627386 Original change's description: > [array] Move Array#sort pre-processing to Torque > > This CL removes the "PrepareElementsForSort" runtime function, and > replaces it with a simpler version in Torque. The biggest difference > is that certain sparse configurations no longer have a fast-path. > > The Torque pre-processing step replaces the existing Torque mechanism that > copied already pre-processed elements into the "work" FixedArray. The Torque > compacting works as follows: > - Iterate all elements from 0 to {length} > - If the element is the hole: Do nothing. > - If the element is "undefined": Increment undefined counter. > - In all other cases, push the element into the "work" FixedArray. > > Then the "work" FixedArray is sorted as before. Writing the elements from > the "work" array back into the receiver, after sorting, has three steps: > 1. Copy the sorted elements from the "work" FixedArray to the receiver. > 2. Add previously counted number of "undefined" to the receiver. > 3. Depending on the backing store either delete properties or > set them to the Hole up to {length}. > > Bug: v8:8714 > Change-Id: I14eccb7cfd2e4618bce2a85cba0689d7e0380ad2 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1619756 > Commit-Queue: Simon Zünd <szuend@chromium.org> > Reviewed-by: Tobias Tebbi <tebbi@chromium.org> > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Cr-Commit-Position: refs/heads/master@{#61812} TBR: jgruber@chromium.org Bug: v8:8714 Change-Id: If7613f6e5f37c5e0d649e8192195594bc6c32100 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627977 Commit-Queue: Simon Zünd <szuend@chromium.org> Auto-Submit: Simon Zünd <szuend@chromium.org> Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#61827}
-
Simon Zünd authored
This reverts commit 2b0ac2fb. Reason for revert: Breaks scrollingcoordinator/non-fast-scrollable-region-nested.html layout test on https://ci.chromium.org/p/v8/builders/ci/V8-Blink%20Linux%2064/32241 Original change's description: > [array] Move Array#sort pre-processing to Torque > > This CL removes the "PrepareElementsForSort" runtime function, and > replaces it with a simpler version in Torque. The biggest difference > is that certain sparse configurations no longer have a fast-path. > > The Torque pre-processing step replaces the existing Torque mechanism that > copied already pre-processed elements into the "work" FixedArray. The Torque > compacting works as follows: > - Iterate all elements from 0 to {length} > - If the element is the hole: Do nothing. > - If the element is "undefined": Increment undefined counter. > - In all other cases, push the element into the "work" FixedArray. > > Then the "work" FixedArray is sorted as before. Writing the elements from > the "work" array back into the receiver, after sorting, has three steps: > 1. Copy the sorted elements from the "work" FixedArray to the receiver. > 2. Add previously counted number of "undefined" to the receiver. > 3. Depending on the backing store either delete properties or > set them to the Hole up to {length}. > > Bug: v8:8714 > Change-Id: I14eccb7cfd2e4618bce2a85cba0689d7e0380ad2 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1619756 > Commit-Queue: Simon Zünd <szuend@chromium.org> > Reviewed-by: Tobias Tebbi <tebbi@chromium.org> > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Cr-Commit-Position: refs/heads/master@{#61812} TBR=peter.wm.wong@gmail.com,jgruber@chromium.org,tebbi@chromium.org,szuend@chromium.org Change-Id: If1c1bc07f38dfbd4bf6b6ce8f9d70714e7526877 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:8714 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627976Reviewed-by:
Simon Zünd <szuend@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#61814}
-
Simon Zünd authored
This CL removes the "PrepareElementsForSort" runtime function, and replaces it with a simpler version in Torque. The biggest difference is that certain sparse configurations no longer have a fast-path. The Torque pre-processing step replaces the existing Torque mechanism that copied already pre-processed elements into the "work" FixedArray. The Torque compacting works as follows: - Iterate all elements from 0 to {length} - If the element is the hole: Do nothing. - If the element is "undefined": Increment undefined counter. - In all other cases, push the element into the "work" FixedArray. Then the "work" FixedArray is sorted as before. Writing the elements from the "work" array back into the receiver, after sorting, has three steps: 1. Copy the sorted elements from the "work" FixedArray to the receiver. 2. Add previously counted number of "undefined" to the receiver. 3. Depending on the backing store either delete properties or set them to the Hole up to {length}. Bug: v8:8714 Change-Id: I14eccb7cfd2e4618bce2a85cba0689d7e0380ad2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1619756 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#61812}
-
- 23 May, 2019 1 commit
-
-
Jaroslav Sevcik authored
Bug: chromium:963925 Change-Id: I92c6899ac188e0f3248e1cee93b1a7e28001e29b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1627540Reviewed-by:
Sergiy Belozorov <sergiyb@chromium.org> Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#61806}
-
- 20 May, 2019 1 commit
-
-
Peter Marshall authored
These were leftover in another directory and can be incorporated into our standard benchmark runner. We already had some Array slice cases in js-perf-test so just add some of the important cases from the other directory to the existing implementation. Bug: v8:9254 Change-Id: I4cc235b8d3719ecd729f23fe9705ea36d445c340 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1617258 Auto-Submit: Peter Marshall <petermarshall@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#61640}
-
- 15 May, 2019 3 commits
-
-
Frank Tang authored
Bug: v8:9153 Change-Id: I48adc554736b19507da318a157ef2f23bf7cbd52 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1610216Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#61549}
-
Z Duong Nguyen-Huu authored
Bug: v8:6831 Change-Id: If3084304b4759f0c1a6e930d66a45f6c9d51eabd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1612166Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com> Cr-Commit-Position: refs/heads/master@{#61545}
-
Nico Hartmann authored
Bug: v8:9240 Change-Id: I704e0932b00baf84c4203baa8336809b250855d9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1611681 Commit-Queue: Nico Hartmann <nicohartmann@google.com> Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#61507}
-
- 11 May, 2019 1 commit
-
-
Z Duong Nguyen-Huu authored
Bug: v8:6831 Change-Id: I4d244771629a1c4785353f125d919793bdf37267 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1604408Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com> Cr-Commit-Position: refs/heads/master@{#61430}
-
- 07 May, 2019 1 commit
-
-
Nico Hartmann authored
This cl also adds a separate test suite for BigInts Bug: v8:9213 Change-Id: I57271eed0f9c33a543fe15550964d55e3df3e963 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1596728 Commit-Queue: Nico Hartmann <nicohartmann@google.com> Reviewed-by:
Georg Neis <neis@chromium.org> Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Tamer Tas <tmrts@chromium.org> Cr-Commit-Position: refs/heads/master@{#61282}
-
- 04 May, 2019 1 commit
-
-
Sergiy Belozorov authored
Overall, total test runtime that was wasted due to timeouts is 3420 seconds in the last 2 weeks. Even with 4 retries, assuming all of them time out, needed additional capacity is under 2 hours per week. Based on this analysis, I think it's safe to land this CL. Note that this is not intended as a long-term solution of the timeout problem, but rather a temporary solution to prevent ongoing errors. Proper investigation and correct long-term solution are still needed and tracked in the bug. R=machenbach@chromium.org, tmrts@chromium.org Bug: chromium:841700 Change-Id: Id16e6b784fa85bb9e28ed8c6b267b583636e2dc1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1593342Reviewed-by:
Tamer Tas <tmrts@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#61224}
-
- 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}
-
- 25 Apr, 2019 2 commits
-
-
Sergiy Belozorov authored
TBR=machenbach@chromium.org Bug: chromium:880724 Change-Id: I6006bb642cab4e9dfcfb4cba43eeb959fe01f046 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1584327 Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Reviewed-by:
Sergiy Belozorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#61025}
-
peterwmwong authored
It shipped in Chrome 73. Bug: v8:6890 Change-Id: Idd8c98cf05a0d6e8fa58c5b0a34d079631f68b1b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1582879Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Mathias Bynens <mathias@chromium.org> Commit-Queue: Peter Wong <peter.wm.wong@gmail.com> Cr-Commit-Position: refs/heads/master@{#61005}
-
- 16 Apr, 2019 1 commit
-
-
Sergiy Belozorov authored
The test is currently passing at over 90% of its timeout both on desktop and Android devices and already occasionally failing due to timeouts on Android. R=jarin@chromium.org, mvstanton@chromium.org No-Try: true No-Tree-Checks: true Bug: chromium:841700 Change-Id: Id1ba078d6a730d304935407426bdbfd0588a138b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1569429Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#60868}
-
- 12 Apr, 2019 1 commit
-
-
Sergiy Belozorov authored
This is not fixing the root cause of the flakiness, but prevents us from loosing data in the short to medium term as investigation proved to be difficult and will likely take even more time. R=machenbach@chromium.org, tmrts@chromium.org Bug: chromium:872257 Change-Id: Id5fbd0a00058f8612089ee4d6a858193924bd868 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1564204 Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#60814}
-
- 25 Mar, 2019 1 commit
-
-
Sigurd Schneider authored
Bug: v8:8557 Change-Id: I213b5944de72eb09a18e44789539b6b420e68068 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1538117Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#60430}
-
- 21 Mar, 2019 2 commits
-
-
Sergiy Belozorov authored
R=machenbach@chromium.org, tmrts@chromium.org Bug: chromium:923304 Change-Id: I65898b7edea8d696d957a8ba19809484e663cb27 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1533864 Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#60399}
-
Sergiy Belozorov authored
The original config will be removed after infra-side change will land and start using new configs. R=machenbach@chromium.org, tmrts@chromium.org Bug: chromium:923304 Change-Id: I5323f0d01724cef2472592bd8e5beb15de232346 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1533863Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#60395}
-
- 20 Mar, 2019 1 commit
-
-
Sigurd Schneider authored
This reverts commit 62a8bdca. Reason for revert: Test times out on atom Original change's description: > [js-perf-test] Add more WeakMap perf tests > > Change-Id: I46eb94e58fc4da55cb1b2adb9ffdbb09e5e33a5d > Bug: v8:8557 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1530800 > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> > Commit-Queue: Sigurd Schneider <sigurds@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60326} TBR=ulan@chromium.org,jarin@chromium.org,sigurds@chromium.org Change-Id: I88ae85bea2ad04db11137a602bd3d8ee6978fa04 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:8557 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1532061Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#60353}
-
- 19 Mar, 2019 1 commit
-
-
Sigurd Schneider authored
Change-Id: I46eb94e58fc4da55cb1b2adb9ffdbb09e5e33a5d Bug: v8:8557 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1530800Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#60326}
-
- 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}
-
- 06 Mar, 2019 1 commit
-
-
Sergiy Belozorov authored
R=ulan@chromium.org Bug: chromium:936713 Change-Id: If3361023fa6fecfc070028ef505ca1ab1ec1d568 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1505800Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Sergiy Belozorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#60066}
-
- 05 Mar, 2019 1 commit
-
-
Frank Tang authored
This is in preparation for the removal of Unibrow. Bug: v8:8362 Change-Id: Icb969457e71d64d765eaf0fd1d0b8b9c6b6eb388 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1490572 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
Mathias Bynens <mathias@chromium.org> Cr-Commit-Position: refs/heads/master@{#60042}
-
- 04 Mar, 2019 1 commit
-
-
peterwmwong authored
Bug: v8:8906 Change-Id: I61c04471530ecf8b97e1e6a0670f52f55232395e Reviewed-on: https://chromium-review.googlesource.com/c/1497517 Commit-Queue: Peter Wong <peter.wm.wong@gmail.com> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#60009}
-
- 20 Feb, 2019 1 commit
-
-
Matt Gardner authored
Change-Id: I808ce4d0089accd3f6afaeab98bd6237e169f793 Reviewed-on: https://chromium-review.googlesource.com/c/1475915 Commit-Queue: Matt Gardner <magardn@microsoft.com> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#59747}
-
- 15 Feb, 2019 1 commit
-
-
Frank Tang authored
$ python -u tools/run_perf.py --binary-override-path out/x64.release/d8 --filter "JSTests/Strings/StringToLocaleCase" test/js-perf-test/JSTests.json INFO >>> Running suite: JSTests/Strings/StringToLocaleCase INFO >>> Stdout (#1): StringToLocaleUpperCaseTR-Strings(Score): 622 StringToLocaleLowerCaseTR-Strings(Score): 728 StringToLocaleUpperCase-Strings(Score): 1129 StringToLocaleLowerCase-Strings(Score): 1548 Bug: v8:8839 Change-Id: I35e20c84614e99cb84ae51c175ac6b1cd53ad3a6 Reviewed-on: https://chromium-review.googlesource.com/c/1469327 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#59615}
-
- 14 Feb, 2019 1 commit
-
-
Frank Tang authored
$ python -u tools/run_perf.py --binary-override-path out/x64.release/d8 --filter "JSTests/Strings/StringNormalize" test/js-perf-test/JSTests.json INFO >>> Running suite: JSTests/Strings/StringNormalize INFO >>> Stdout (#1): StringNormalize-Strings(Score): 4014 StringNormalizeNFD-Strings(Score): 742 StringNormalizeNFKC-Strings(Score): 3066 StringNormalizeNFKD-Strings(Score): 739 Bug: v8:8844 Change-Id: Ic941bafa82cead9cd0110ad7ac46e528d481189b Reviewed-on: https://chromium-review.googlesource.com/c/1470964 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#59612}
-
- 11 Feb, 2019 1 commit
-
-
Mythri authored
The spec specifies that a non-true return values from the trap functions should be treated as error in the strict mode. With the new lazy feedback effort inferring the language mode is expensive and causes regression on these tests. Since the test doesn't actually need to test this, fixing them to return true would help test the performance of calling the trap without the unnecessary overhead of inferring the language mode. Bug: chromium:925289 Change-Id: Ib650c3210ee260296257ae3b56174099a5492675 Reviewed-on: https://chromium-review.googlesource.com/c/1462959 Commit-Queue: Mythri Alle <mythria@chromium.org> Reviewed-by:
Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#59505}
-
- 09 Feb, 2019 1 commit
-
-
Z Duong Nguyen-Huu authored
Bug: v8:6831 Change-Id: I67e4d9f39576a4067dad59b18b3b4bf04bcdcb99 Reviewed-on: https://chromium-review.googlesource.com/c/1461166 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#59486}
-
- 07 Feb, 2019 1 commit
-
-
Frank Tang authored
Just add tests so we can observe the number first. Got the following results $ python -u tools/run_perf.py --binary-override-path out/x64.release/d8 --filter "JSTests/Intl" test/js-perf-test/JSTests.json INFO >>> Running suite: JSTests/Intl INFO >>> Stdout (#1): NewIntlCollator-Intl(Score): 161 NewIntlDateTimeFormat-Intl(Score): 9.73 NewIntlNumberFormat-Intl(Score): 18.6 NewIntlPluralRules-Intl(Score): 18.5 NewIntlListFormat-Intl(Score): 19.4 NewIntlRelativeTimeFormat-Intl(Score): 18.7 Bug: chromium:928098 Change-Id: I59f28393af8f868de639dcb81a7b2f69ce2f0eba Reviewed-on: https://chromium-review.googlesource.com/c/1455717 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#59424}
-
- 17 Jan, 2019 1 commit
-
-
Ujjwal Sharma authored
Add benchmarks for String.prototype.startsWith in order to keep track of performance ahead of the torque port. Bug: v8:8400 Change-Id: I0276b84b315024bba1a0d6f761ee2c6cf2c516a2 Reviewed-on: https://chromium-review.googlesource.com/c/1416070 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#58870}
-
- 10 Jan, 2019 2 commits
-
-
Jakob Gruber authored
This reverts commit 5dee355f. Reason for revert: https://ci.chromium.org/p/v8-internal/builders/luci.v8-internal.ci/v8_linux64_perf_1/4282 Original change's description: > [test] add perf tests for String.p.startsWith > > Add performance tests for String.prototype.startsWith ahead of port to > torque in order to keep track of how performance is affected. > > Bug: v8:8400 > Change-Id: Ifc753a6f13da20c1760e545a99fd693717e3acc6 > Reviewed-on: https://chromium-review.googlesource.com/c/1402934 > Commit-Queue: Jakob Gruber <jgruber@chromium.org> > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Cr-Commit-Position: refs/heads/master@{#58685} TBR=jgruber@chromium.org,usharma1998@gmail.com Change-Id: I5855b08fa5e55ab8594185a0a84a26f567e2b9d3 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:8400 Reviewed-on: https://chromium-review.googlesource.com/c/1404446Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#58697}
-
Ujjwal Sharma authored
Add performance tests for String.prototype.startsWith ahead of port to torque in order to keep track of how performance is affected. Bug: v8:8400 Change-Id: Ifc753a6f13da20c1760e545a99fd693717e3acc6 Reviewed-on: https://chromium-review.googlesource.com/c/1402934 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#58685}
-
- 17 Dec, 2018 1 commit
-
-
Sigurd Schneider authored
Change-Id: I3530c3f50fdb805d68099108dc33d93abe6bdb39 Bug: v8:8344 Reviewed-on: https://chromium-review.googlesource.com/c/1379931Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#58267}
-
- 14 Dec, 2018 1 commit
-
-
Jakob Kummerow authored
The new ObjectPtr design makes non-inlined helper functions a little more expensive because "this" is always a pointer where pass-by-value would be more efficient, which is an issue for functions whose size puts them right at the threshold of getting inlined or not. String::Get falls into this category when called from RegExpFlagsFromString. In this case, we can do even better than restoring inlineability by fine-tuning the control flow a bit. This should repair the regression in crbug.com/910573 Bug: chromium:910573 Change-Id: Ie6b68ef01cd978ec502d8d6c1da788c77422dce7 Reviewed-on: https://chromium-review.googlesource.com/c/1369087 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#58234}
-
- 11 Dec, 2018 1 commit
-
-
peterwmwong authored
This patch adds micro-benchmarks for TypedArray#join with and without a separator. The benchmark can be used to measure any TypedArray#join optimizations we implement in the future. Test: tools/run_perf.py --binary-override-path=out/x64.release/d8 \ --filter JSTests/TypedArrays/Join \ test/js-perf-test/JSTests.json Bug: v8:7624 Change-Id: I526af50da0eff400d21b807ba30a9de2c3d87476 Reviewed-on: https://chromium-review.googlesource.com/c/1369333Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Sergiy Belozorov <sergiyb@chromium.org> Commit-Queue: Peter Wong <peter.wm.wong@gmail.com> Cr-Commit-Position: refs/heads/master@{#58163}
-
- 06 Dec, 2018 1 commit
-
-
tzik authored
This replaces Runtime_RunMicrotasks with Runtime_PerformMicrotaskCheckpoint. RunMicrotasks forcibly runs Microtasks even when the microtasks are suppressed, and may causes nested Microtasks in a problematic way. E.g. that confuses v8::MicrotasksScope::IsRunningMicrotasks() and GetEnteredOrMicrotaskContext(). OTOH, PerformMicrotaskCheckpoint() doesn't run cause the failure as it respects the microtask suppressions. As all existing tests don't call RunMicrotasks() in the suppressed situation (like Promise.resolve().then(()=>{%RunMicrotasks();})), this change should not affect to these tests. Change-Id: Ib043a0cc8e482e022d375084d65ea98a6f54ef3d Reviewed-on: https://chromium-review.googlesource.com/c/1360095Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Taiju Tsuiki <tzik@chromium.org> Cr-Commit-Position: refs/heads/master@{#58068}
-
- 07 Nov, 2018 1 commit
-
-
Frank Tang authored
This is a bit of a performance bottleneck currently and we're planning on improving performance by adding caching. These benchmarks will allow us to measure the improvements Add benchmark tests for String.prototype.localeCompare() Date.prototype.toLocaleString() Date.prototype.toLocaleDateString() Date.prototype.toLocaleTimeString() Number.prototype.toLocaleString() Run with python -u tools/run_perf.py --binary-override-path \ out/x64.release/d8 --filter "JSTests/Strings/StringLocaleCompare" \ test/js-perf-test/JSTests.json python -u tools/run_perf.py --binary-override-path \ out/x64.release/d8 --filter "JSTests/Dates" \ test/js-perf-test/JSTests.json python -u tools/run_perf.py --binary-override-path \ out/x64.release/d8 --filter "JSTests/Numbers" \ test/js-perf-test/JSTests.json Before the landing of dffaff77 git reset --hard 474a6d63 got StringLocaleCompare-Strings(Score): 13240000 toLocaleDateString-Dates(Score): 1877000 toLocaleString-Dates(Score): 1197000 toLocaleTimeString-Dates(Score): 2147000 toLocaleDateString-Dates(Score): 1908000 After the landing of dffaff77 git reset --hard dffaff77 got StringLocaleCompare-Strings(Score): 97182 toLocaleDateString-Dates(Score): 10436 toLocaleString-Dates(Score): 10436 toLocaleTimeString-Dates(Score): 10669 toLocaleString-Numbers(Score): 2876 Bug: chromium:901748 Change-Id: Ibfea85fe668f1bfaacb2dfe08368cd920d2bbfc6 Reviewed-on: https://chromium-review.googlesource.com/c/1318099Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#57323}
-