Repository navigation
Conversation
The detector and exact_answers remember each series' top-k keys over the last N windows; a key in the current top-k that none of them held is new, emitted as asap.topk.new and as an OTLP log event. Adds the top-k scenario (200 Zipf routes; a new route takes 15% of traffic at minute 10) and its dashboard.
zzylol
force-pushed
the
feat/topk-novelty
branch
from
October 13, 2026 00:20
d26cfaf to
671c431
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
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.
Part 6 of the RFC 0001 stack: use case 3, heavy hitters and novelty.
The detector and
exact_answersremember each series' top-k keys over the last 10 windows. A key in the current top-k that none of those windows held is new: it is emitted asasap_topk_newand as an OTLP log event. The scenario has 200 Zipf routes, and at minute 10 a new route takes 15% of traffic. Sketch: Count-Min 4 × 2048 with a 10-slot heap per attribute key (per_attribute: [http.route]).Result (56-core x86 server, 1-minute windows)
/new/hot-routewas flagged by both methods in the window it appeared, at rank 2.With only 200 keys in 2,048 columns there are no collisions. The accuracy-vs-width experiment in a later PR uses 100,000 keys.
cargo fmt --check,cargo clippy --all-targets --features otap-engine,stream-benchmark -- -D warningsandcargo test --features otap-engine,stream-benchmarkpass at this PR's head.