-
Notifications
You must be signed in to change notification settings - Fork 25.6k
ESQL: Benchmark TO_LOWER and TO_UPPER #123268
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
Conversation
This adds a microbenchmark for TO_LOWER and TO_UPPER. They are quite common probably could use some optimizing.
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
|
I haven't a clue why TO_UPPER is slower in the microbenchmark. I swapped the other and ran them and got the same result. |
| } | ||
| } | ||
| } | ||
| case "to_lower" -> checkBytes(operation, actual, new BytesRef[] { new BytesRef("foo"), new BytesRef("bar") }); |
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.
Nitty nit: wondering if it make sense extracting the BytesRef[] as it's used both in page generation and the check... though probably not. :)
luigidellaquila
left a comment
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.
LGTM
💚 Backport successful
|
This adds a microbenchmark for TO_LOWER and TO_UPPER. They are quite common probably could use some optimizing.
This adds a microbenchmark for TO_LOWER and TO_UPPER. They are quite common probably could use some optimizing.