This repository was archived by the owner on Aug 26, 2026. It is now read-only.
receive/handler: deamplify writes through labels - #99
Open
GiedriusS wants to merge 1 commit into
Open
Conversation
Currently, the tenant field is a separate field in WriteRequest. This is one of the reasons why we have such a write amplification - we get 200 req/s on HTTP level but 100k/s on gRPC level. Ordinarily, we need to send each tenant's data individually. But, we could embed multiple tenant's data in one gRPC request. Do that by using labels, just like how we receive the data right now. Signed-off-by: Giedrius Statkevičius <giedrius.statkevicius@vinted.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Currently, the tenant field is a separate field in WriteRequest. This is one of the reasons why we have such a write amplification - we get 200 req/s on HTTP level but 100k/s on gRPC level. Ordinarily, we need to send each tenant's data individually. But, we could embed multiple tenant's data in one gRPC request. Do that by using labels, just like how we receive the data right now.