Repository navigation
DOC-7265 Update RDI FAQ throughput to the Flink baseline - #4475
Open
andy-stark-redis wants to merge 1 commit into
Open
andy-stark-redis wants to merge 1 commit into
andy-stark-redis wants to merge 1 commit into
Conversation
Replace the 10,000 records per second per processing unit answer in the FAQ with the Flink processor figures from the "When to use RDI" page (20K CDC, 60K full sync, about 1KB records, no transformations), note that the classic processor supports about half, and link to that page. I removed the processing-unit sentences, including "one processing unit is enough for a relational database", because they only made sense with the old per-core figure and nothing on the Flink side confirms the concept still applies. The same 10,000 figure remains in the High throughput bullet of the RDI overview page; it is deliberately out of scope here and noted on the ticket. Mirko Ortensi flagged the FAQ as outdated in a review comment on the RDI + Azure Managed Redis blog draft. Learned: FAQ throughput figures should track rdi-when-to-use.md, not be restated independently Directive: do not reintroduce a per-processing-unit throughput claim without engineering confirming it for the Flink processor Gaps: figures copied from the when-to-use embed, not re-measured; overview page still says 10,000 Ticket: DOC-7265 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Contributor
Contributor
Contributor
🧠 Redis MemoryFound 5 related items from repository history (5 new this commit):
Memory updated at e07bc83 |
Contributor
Author
|
Thanks @dwdougherty ! |
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.
Summary
Ticket: DOC-7265
For reviewers
content/embeds/rdi-when-to-use.md, not re-measured.redis-data-integration/_index.mdstill says about 10,000 records per second.🤖 Generated with Claude Code
Note
Low Risk
Documentation-only change to FAQ throughput figures; no code or runtime behavior is affected.
Overview
Updates the FAQ answer for How much data can RDI process? to reflect Flink and classic processor limits instead of the old processing-unit model (~10K records/sec per CPU core).
The new text states up to 20K records/sec for CDC and 60K for full sync with Flink (about half for classic), with the same ~1KB, no-transformations assumptions, and points readers to When to use RDI for full throughput and data-size guidance. The one processing unit is enough wording is removed.
Reviewed by Cursor Bugbot for commit e07bc83. Bugbot is set up for automated code reviews on this repo. Configure here.