Repository navigation
Conversation
Add two gauges for the in-memory events index of the open hot chunks: stellar_rpc_events_inmemory_index_terms and stellar_rpc_events_inmemory_index_dense_terms, each with a state label (ingesting, completed). A collector reads the published hot chunks at scrape time. A hot chunk that has terms logs its warmup time and term count when it opens. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
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.
What
Adds two gauges for the in-memory events index of the open hot chunks.
stellar_rpc_events_inmemory_index_termsstatestellar_rpc_events_inmemory_index_dense_termsstatestatehas two values:ingesting: the chunk that ingest writes to.completed: the sum of all other open hot chunks.Why
The in-memory index is the main memory cost of a hot chunk. These gauges show its size and how many terms are dense, so that we can tune it.
Scope
In scope:
rpcv2only.ConcurrentBitmaps.AddTonow increments an atomic counter when a term becomes dense. This is the only change on the ingest path.Not in scope:
Behavior
ingestingchunk is the newest published chunk. This is correct because only startup and the chunk boundary publish a chunk, and the boundary publishes the next chunk id.Statsreads the dense count before the term count.AddToadds a term to the map before it counts the term as dense, sodense_termsis never larger thanterms.statevalues are always exported. They are zero until startup opens the query registry.🤖 Generated with Claude Code