Skip to content

Commit 458b491

Browse files
viiryaclaudealamb
authored
perf: optimize left function by eliminating double chars() iteration (#19571)
For negative n values, the function was calling string.chars() twice: 1. Once to count total characters 2. Again to take the prefix This optimization collects chars into a reusable buffer once per row for the negative n case, eliminating the redundant iteration. Benchmark results (negative n, which triggers the optimization): - size=1024: 71.323 µs → 52.760 µs (26.0% faster) - size=4096: 289.62 µs → 212.23 µs (26.7% faster) Benchmark results (positive n, minimal overhead): - size=1024: 24.465 µs → 24.691 µs (0.9% slower) - size=4096: 96.129 µs → 97.078 µs (1.0% slower) The dramatic improvement for negative n cases far outweighs the negligible overhead for positive n cases. ## Which issue does this PR close? <!-- We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. For example `Closes #123` indicates that this PR will close issue #123. --> - Closes #. ## Rationale for this change <!-- Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed. Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes. --> ## What changes are included in this PR? <!-- There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR. --> ## Are these changes tested? <!-- We typically require tests for all PRs in order to: 1. Prevent the code from being accidentally broken by subsequent changes 2. Serve as another way to document the expected behavior of the code If tests are not included in your PR, please explain why (for example, are they covered by existing tests)? --> ## Are there any user-facing changes? <!-- If there are user-facing changes then we may require documentation to be updated before approving the PR. --> <!-- If there are any breaking changes to public APIs, please add the `api change` label. --> --------- Co-authored-by: Claude Sonnet 4.5 <[email protected]> Co-authored-by: Andrew Lamb <[email protected]>
1 parent 45fb0b4 commit 458b491

File tree

1 file changed

+12
-3
lines changed
  • datafusion/functions/src/unicode

1 file changed

+12
-3
lines changed

datafusion/functions/src/unicode/left.rs

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -139,14 +139,23 @@ fn left_impl<'a, T: OffsetSizeTrait, V: ArrayAccessor<Item = &'a str>>(
139139
n_array: &Int64Array,
140140
) -> Result<ArrayRef> {
141141
let iter = ArrayIter::new(string_array);
142+
let mut chars_buf = Vec::new();
142143
let result = iter
143144
.zip(n_array.iter())
144145
.map(|(string, n)| match (string, n) {
145146
(Some(string), Some(n)) => match n.cmp(&0) {
146147
Ordering::Less => {
147-
let len = string.chars().count() as i64;
148-
Some(if n.abs() < len {
149-
string.chars().take((len + n) as usize).collect::<String>()
148+
// Collect chars once and reuse for both count and take
149+
chars_buf.clear();
150+
chars_buf.extend(string.chars());
151+
let len = chars_buf.len() as i64;
152+
153+
// For negative n, take (len + n) chars if n > -len (avoiding abs() which panics on i64::MIN)
154+
Some(if n > -len {
155+
chars_buf
156+
.iter()
157+
.take((len + n) as usize)
158+
.collect::<String>()
150159
} else {
151160
"".to_string()
152161
})

0 commit comments

Comments
 (0)