Make the CPU eviction order configurable - #937
Merged
Merged
Conversation
Adds a prod-cached class for requests that only stream cached outputs, so they can be evicted without a wasm burn rate.
billettc
approved these changes
Sep 16, 2026
This was referenced Sep 16, 2026
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.
Adds
EvictorConfig.Order, the list of request classes eviction may cancel, least important first (ParseEvictionOrder("dev,prod-cached,prod-catchup")). A class left out is never cancelled. The default isdev,prod-cached,prod-catchup, so live production requests are no longer cancelled unlessprod-liveis added to the order.New class
prod-cached: a production request that has not processed a block on tier1 yet, meaning it only streams outputs cached by tier2. It runs no wasm on tier1, so:MinBurnCoresdoes not apply to it (MinAgestill does).Cooldown, measures what it freed.Within a class, requests are still cut highest burn first, now with oldest first on a tie (which is the only ordering among
prod-cachedrequests).dev-onlymode still restricts eviction todev, whatever the order says.The
--substreams-tier1-cpu-eviction-orderflag has to be added in firehose-core.