feat: extend udf_overhead benchmark w/ sub-str example#358
Open
crepererum wants to merge 1 commit intomainfrom
Open
feat: extend udf_overhead benchmark w/ sub-str example#358crepererum wants to merge 1 commit intomainfrom
udf_overhead benchmark w/ sub-str example#358crepererum wants to merge 1 commit intomainfrom
Conversation
12e88dd to
4074d79
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For #28.
Results
The per-row overhead looks better if we pass larger data around, likely because the cost to manage python objects gets relatively lower. However I'm somewhat surprised that the per-call overhead for both Python and the plain WASM wrapper is soo large. Gonna need to check the reason for this in a follow-up.