- Notifications
You must be signed in to change notification settings - Fork 727
The serialized TEvReadSet takes up a lot of memory #18289
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
The serialized TEvReadSet takes up a lot of memory #18289
Conversation
| ⚪ |
| ⚪ |
1119120 to b5924e8 Compare | ⚪
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
| ⚪
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
9d4ad3c into ydb-platform:stable-24-4
Changelog entry
Issue #18290
The TEvReadSet message can be sent again. When it was first sent, it was serialized and stored as a string. It turned out that the serialized message takes up a lot of memory space. For transactions with a large number of participants, this takes up a lot of space.
I changed it so that a copy of the data is stored to create a TEvReadSet when resending.
Changelog category
Description for reviewers
...