Repository navigation
benchmarks: drop the first engine-stage run (two answers in one record) - #10
Merged
Merged
Conversation
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
1 participant
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.
The first run of stage 1 (native TTS, LLM on CPU) reported 55.89 s of gaps. Its raw record holds 15 sentences and 143 s of audio, about twice any other run, and contains two different stories interleaved (two openings, two endings). It is two answers in one record, not a measurement of one answer, so it is dropped from the table and the stages figure. Stage 1 now shows its one valid run (5.56 s first audio, 3 gaps / 0.18 s). Nothing in the README used this run.