-
Notifications
You must be signed in to change notification settings - Fork 509
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
[Feature Request] Optimizer for sortable TAG field #4376
Comments
hey @keithchew thanks for reaching out! Glad that you're playing with the Sort optimisations. I would love to hear your inputs for the TAG implementation. |
Currently, I only have the dataset which I plan to use for the test, ie creating 2mil sets with both numeric and tag numbers:
then, using the profile to compare:
The first profile will be optimized as it has a numeric field. The second will not be optimized as it is not numeric, but hopefully with an enhancement to the Optimizer, it can be improved to be comparable to the first. |
This issue is stale because it has been open for 60 days with no activity. |
I have been testing the new sortby Optimizer and so far have been very happy with the results, achieving performance gains up to 100x in some use cases.
Currently the optimizer only applies to numeric fields in the sortby, I would like some information or thoughts on whether the optimizer can be extended to cover tag fields.
Perhaps initially just some feedback on whether this is feasible or not, and if yes, I would be happy to jump deeper into the code and do some experiments.
The text was updated successfully, but these errors were encountered: