Pipeline count_all_scheduled_jobs for significantly faster execution#822
Merged
PatrickTulskie merged 2 commits intoJul 8, 2026
Merged
Conversation
This was referenced May 14, 2026
PatrickTulskie
self-requested a review
May 20, 2026 19:34
PatrickTulskie
approved these changes
Jul 8, 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.
Problem
count_all_scheduled_jobsissues one sequentialLLENRedis call per delayed timestamp. With many delayed jobs, this becomes a significant bottleneck, especially when called from metric collectors like yabeda-resque during Prometheus scrapes.On our production system (20k timestamps, 36k delayed jobs) this single method took 5.6 seconds, causing Prometheus scrape timeouts. For the same number of jobs and timestamps, the pipelined implementation took only ~300ms.
18.6x faster.
Solution
Pipeline all
LLENcalls in batches of 10,000 to avoid blocking the Redis thread for too long while still being significantly faster than sequential calls.Production benchmarks
We have run this implementation in production by inclduing it in https://github.com/jbockler/yabeda-resque first See PR, so I am confident this works in practice. We have seen a reduction of query times by an order of magnitide confirming our simple measerement above.