-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 Cow<str> in TableReference to Arc<str> #9764
Comments
Before we make a PR to do this I think it would be worth creating a POC / demonstrate that it would actually improve performance The natural way to test would be cargo bench --bench sql_planner |
if no one already trying that, I'll check it |
Other thing that comes to my mind, is we prob want to use only 1 String type in DF. |
I think the use cases of them depends, not always one beats others. |
I suggest Arc for anything that will be copied around and |
Consider the atomic operation cost, I doubt that
|
I'm still on it folks, it requires to go through all the analyzer. |
note that #9595 makes substantial changes to the code, so unless you build off that PR you'll likely end up with many many conflicts |
Thanks for letting me know, I made a draft #9824 to play a little but with benches |
with
|
Which one does this compare with, Arc or main branch? |
both comparisons are vs main branch. so let me know your thoughts, |
the PR is #9824 I'm still hesitating between |
One vote for |
But |
If TableReference is mostly read but has little mutation, I would go for The benchmark might change if the codebase grows, so we need to consider the role of the TableReference besides the benchmark. The benchmark for me in this PR is to ensure the change is better than the previous ( |
Originally posted by @alamb in #9595 (comment)
A benchmark for this is required.
The text was updated successfully, but these errors were encountered: