Adds blog post about RedisWorker. #170
Open
Conversation
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
bmbouter
reviewed
Jan 16, 2026
| --- | ||
| # RedisWorker Delivers 2.3x Performance Improvement | ||
|
|
||
| This performance breakthrough came from an innovative collaboration with AI. We explained the PostgreSQL load challenges we were facing to an AI assistant, which designed an algorithm that offloads resource locking to Redis while maintaining task ordering guarantees. The AI then helped write the implementation code and test suite, dramatically accelerating our development process. This approach allowed us to rapidly prototype and validate the solution, demonstrating how AI can be a powerful tool for tackling complex architectural challenges. |
Member
There was a problem hiding this comment.
I'd make this a section called AI Driven Development
bmbouter
reviewed
Jan 16, 2026
| - tasking | ||
| - redis | ||
| --- | ||
| # RedisWorker Delivers 2.3x Performance Improvement |
Member
There was a problem hiding this comment.
I'd move this down to the We're excited to ...
bmbouter
reviewed
Jan 16, 2026
|
|
||
| ## Benchmark Results | ||
|
|
||
| Our testing compared the traditional `PulpcoreWorker` implementation against the new `RedisWorker` implementation under identical conditions: |
Member
There was a problem hiding this comment.
Suggested change
| Our testing compared the traditional `PulpcoreWorker` implementation against the new `RedisWorker` implementation under identical conditions: | |
| Our testing compared the existing `PulpcoreWorker` implementation (the default) against the new `RedisWorker` implementation under identical conditions: |
bmbouter
reviewed
Jan 16, 2026
|
|
||
| The performance improvement comes from two key innovations: offloading resource lock coordination to Redis and eliminating the task unblocking mechanism. Here's what changed: | ||
|
|
||
| **Traditional PulpcoreWorker Approach:** |
Member
There was a problem hiding this comment.
Suggested change
| **Traditional PulpcoreWorker Approach:** | |
| **Existing PulpcoreWorker Approach:** |
bmbouter
reviewed
Jan 16, 2026
|
|
||
| - High-volume task processing environments | ||
| - Deployments where Redis is already part of the infrastructure | ||
| - Scenarios where task throughput is critical |
Member
There was a problem hiding this comment.
Consider adding another bullet about environments that struggle with DB CPU load.
bmbouter
reviewed
Jan 16, 2026
|
|
||
| These performance improvements represent a significant step forward for Pulp's scalability. We're continuing to enhance the RedisWorker implementation and explore additional optimizations. | ||
|
|
||
| The RedisWorker implementation will be available soon in upcoming Pulp releases. We encourage users with high-throughput requirements to evaluate it in their environments once released. |
Member
There was a problem hiding this comment.
It would be good to unpack this a bit. It needs to be merged, it needs to be tested in the CI, and then released. I think a numbered list would read nicely (personally).
bmbouter
reviewed
Jan 16, 2026
Comment on lines
+60
to
+65
| By separating resource locking from the main database: | ||
|
|
||
| 1. **Reduced PostgreSQL Load**: Database queries are limited to task CRUD operations, not constant lock checking | ||
| 2. **Faster Lock Operations**: Redis's in-memory operations are significantly faster than database queries | ||
| 3. **Better Scalability**: Workers can check and acquire locks with minimal overhead | ||
| 4. **Improved Throughput**: The system can process more than twice as many tasks per second |
Member
There was a problem hiding this comment.
I think this section needs to be thought through some more. I'm going to think about it some.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.