Repository navigation
Add direct BreakTest DB output and drain pending TimescaleDB batches - #4
Merged
Merged
Conversation
jgaalen
marked this pull request as ready for review
November 6, 2026 06:54
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.
Continues jgaalen/k6#4, which records the implementation history, earlier benchmarks and acceptance reports.
Changes
Add direct BreakTest DB ingestion and native/browser completion watermarks. Reconcile the TimescaleDB shutdown fix with the binary COPY writer from #3. Steady-state sends keep their one-second cadence. Shutdown joins the batch and HTTP-group cleanup workers, drains queued binary rows, and reports exhausted delivery retries. Both writers use the same metric mapping.
Verification