Repository navigation
perf: calculate voice waveform peaks without slice allocations - #1428
Open
MrPunyapal wants to merge 1 commit into
Open
MrPunyapal wants to merge 1 commit into
MrPunyapal wants to merge 1 commit into
Conversation
Contributor
MrPunyapal
force-pushed
the
perf/avoid-voice-waveform-slice-allocations
branch
from
November 3, 2026 05:55
0bcc647 to
fc0f56a
Compare
MrPunyapal
marked this pull request as ready for review
November 3, 2026 06:02
MrPunyapal
force-pushed
the
perf/avoid-voice-waveform-slice-allocations
branch
from
November 3, 2026 21:02
fc0f56a to
c1640d0
Compare
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.
Change
Calculates voice waveform peaks directly from each range instead of allocating sliced arrays. Peak values and boundaries are preserved, including empty input.
Validation
The full JavaScript unit suite passed (225 tests). A synthetic Node benchmark showed about a 3x reduction for 1,200 samples across 10,000 calls, but the application calculates a waveform once per recording, so the real user impact is small and has not been measured in a target browser. This remains a draft pending confirmation that the added complexity is worthwhile.
Summary by CodeRabbit