-
Notifications
You must be signed in to change notification settings - Fork 595
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
perf: optimize json parser #9113
Comments
bench #9195 |
Went through the flame graphs generated in https://buildkite.com/risingwavelabs/main-cron/builds/458#0187c454-58bd-439a-bf57-6f774ea41b80 For queries q0,q1,q2,q3,q7,q8,q10,q14,q15,q17,q18,q20,q21,q22, json parser takes more time than other executors. |
Investigating it |
The |
Another potential cost risingwave/src/common/src/array/mod.rs Lines 481 to 496 in 5fabd2a
|
The |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This issue has been open for 60 days with no activity. If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the You can also confidently close this issue as not planned to keep our backlog clean. |
closed with #17146 and related PRs |
For q17
Now:
Before:
Here's the flamegraph:
Interactive version
The text was updated successfully, but these errors were encountered: