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.

Sign up for GitHub

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

Jump to bottom

Make sure multi-key writes are close in the key range #3504

Open

ma2bd opened this issue Mar 8, 2025 · 0 comments

Assignees

Labels

performance triage

Milestone

Contributor

ma2bd commented Mar 8, 2025

In production, atomic multi-key writes across several ScyllaDB shards are likely to be expensive. (We may to also confirm that ofc)

ma2bd added the triage label

ma2bd added this to the Mainnet milestone

ma2bd assigned afck and ma2bd

ma2bd added this to Storage

ma2bd added the performance label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment