Fyi the regression is already in Chrome 68.0.3440.59. On Wed, Jul 18, 2018 at 12:51 PM, Jakob Gruber <jgru...@chromium.org> wrote:
> Interesting. I can reproduce locally. > > Please open a bug at http://crbug.com/v8/new (and post the link here for > future reference). Thanks! > > On Wed, Jul 18, 2018 at 12:41 PM, <shahar.s...@gmail.com> wrote: > >> Hello. >> >> I've noticed a severe performance regression in a JavaScript Parsing >> libraries <http://sap.github.io/chevrotain/performance/> benchmark >> i've created. This is a *pure* CPU JavaScript engine benchmark, so the >> cause should >> be V8, not Chrome. >> >> On Chrome Stable Version 67.0.3396.99 (Official Build) (64-bit): >> With *V8 6.7.288.46 *I am getting *~2,500* Ops/sec for the Chevrotain >> library. >> >> While On Chrome Canary Version 69.0.3495.0 (Official Build) canary >> (64-bit) >> with *V8 6.9.423 *I am getting* only ~1,000 *Ops/Sec >> >> I also saw a similar issue with Chrome beta/dev channels. >> That is a pretty severe regression... >> >> >> What should I do now? Where can I open a bug? How can I help? >> >> - I've played around with the source code of the Chevrotain but have >> not found any workaround/mitigation yet. >> - I've thought about reproducing the issue in node.js but there is no >> node.js version with V8 6.9 yet. >> >> >> -- -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
