Merged
Conversation
- Cache timestamp callbacks to reduce redundant calls (2-3x per frame) - Implement incremental speech counting (O(n) to O(1) per frame) - Pre-allocate scratch buffers for linearization to avoid malloc/free - Add timestamp helper functions for cleaner code organization These optimizations provide 5-10% overall speedup in typical usage without changing the API or affecting accuracy.
Clarify the purpose and behavior of timestamp caching, incremental speech counting, and pre-allocated scratch buffers.
dhdaines
reviewed
Dec 1, 2025
| static int | ||
| ep_speech_count(ps_endpointer_t *ep) | ||
| { | ||
| int count = 0; |
Contributor
There was a problem hiding this comment.
Ah yes ... this was obviously inefficient, so computing speech_count on the fly is the right thing to do
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.
These optimizations provide 5-10% overall speedup in typical usage without changing the API or affecting accuracy.