GitHub user Tangruilin added a comment to the discussion: support CMS and Top-k for kvrocks
Apologies for submitting such a long proposal all at once — I was too eager and made it difficult to review. I've split out CMS into its own proposal. For Top-K, I'll work on a separate design after CMS is completed. Additionally, regarding the suggestion about the per-key approach, I have a few points I'd like to discuss: 1. Between the options compared above, which do you think is better — Single Key or Per-Column? Personally, I'm leaning toward Single Key. It's simpler to implement, and we can later use MergeOperator to optimize write amplification. 2. I'm not entirely sure I understand how reducing page size helps here. With a single key approach, smaller page sizes don't really improve read performance, since Get() always reads the entire value anyway. Could you elaborate on this?" GitHub link: https://github.com/apache/kvrocks/discussions/3404#discussioncomment-17319190 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
