You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Accessing the dictionary for the lookahead functions cache is a hotspot.
For example a past optimization of creating the lookahead keys using bit operators
yielded a 25% overall performance boost.
Perhaps using ES6 Maps could provide a performance boost
As they have in Jest:
Looks like there is a smaller performance boost (6-9%) for the parsing flow (excluding lexing flow)
in the more complex grammar samples, With a similar regression for a very simple grammar (JSON).
This is probably a worthwhile trade off.
bd82
changed the title
Investigate using ES6 "Map" instead of Object
Micro Optimization - Use ES2015 Maps for Lookahead function Caching.
Sep 17, 2018
* Use ES6 Map instead of a plain object to optimize performance.
Fixes#812.
* Upgrade to Safari 11 browser testing.
And use newer macos versions on saucelabs.
Accessing the dictionary for the lookahead functions cache is a hotspot.
For example a past optimization of creating the lookahead keys using bit operators
yielded a 25% overall performance boost.
Perhaps using ES6 Maps could provide a performance boost
As they have in Jest:
The text was updated successfully, but these errors were encountered: