-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace better-eval with vm #536
Conversation
Added test case similar to the repro that calls select on a variant column containing a large result set |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please do pref test and put numbers in this ticket before and after the change.
Average execution time of testVariantLarge over 10 runs:
|
…op table in the before/after functions
…op table in the before/after functions
…op table in the before/after functions
…op table in the before/after functions
…op table in the before/after functions
…op table in the before/after functions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's add run lint (npm run lint:check -- FILENAME
) for new code. Especially new files could be even changed with npm run lint:fix -- FILENAME
.
what is the average execution time of |
Regarding issue 366
The PR replaces better-eval with vm for converting raw variant strings. The better-eval package creates a new VM for each conversion while this change creates a single VM and re-uses it for all conversions