-
Notifications
You must be signed in to change notification settings - Fork 715
feat: support shared memtable for many orgs #8943
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
Testdino Test Results
|
yaga-simha
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I guess the 1:1 performance comparison for low intensity usecase will be identical but higher the number of orgs the better this solution scales.
Current version will create memtable for each org and streamType. we will create 3000 memtables if you have 1000 orgs and both write logs, metrics and traces. This is unacceptable in some customers.
This PR implement a new feature that we let multiple orgs write to a same memtable by hashing.
You can enable this feature by set env:
This config will maximum create 30 memtables.
Metrics compatible issue
This PR also fixed metrics compatible reduced issue, it is because of we removed
__name__label in the response.