perf: fast integer path in number-to-string for ~38% stringops speedup#505
Merged
perf: fast integer path in number-to-string for ~38% stringops speedup#505
Conversation
Contributor
Benchmark Results (Linux x86-64)
CLI Tool Benchmarks
|
cs01
added a commit
that referenced
this pull request
Apr 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
User-visible win
Programs that build strings by concatenating numbers (e.g. `"item" + i`, `"row-" + id`, logging loops, CSV/JSON formatting) now run noticeably faster. On the `stringops` benchmark:
Any app that formats numbers into strings in a hot loop benefits.
Root cause
`sample` profiling of the stringops benchmark showed ~45% of runtime inside `snprintf` — specifically `__vfprintf` / `__Balloc_D2A` / `__d2b_D2A` / `localeconv_l`. Every `"item" + i` concatenation was calling `snprintf("%.15g", double)`, which on macOS/glibc goes through a slow locale-aware floating-point path even when the value is a small integer.
The old `convertNumberToString` codegen also emitted:
Four passes over the buffer per number.
Fix
Validation