Is your feature request related to a problem? Please describe.
I'm always frustrated when metabase work nonoptimal.
Describe the solution you'd like
Counters are stored in a single KV pair as a usual concatenation of 8-byte counters. Usually, they are updated in a single transaction one by one.
Describe alternatives you've considered
Keep it as is.
Additional context
Originally posted by @roman-khimov in #3856 (comment)
I am not sure if it is worth it, to be honest. Also, it is not clear whether we need it if #3856 (comment) is not solved, cause this is the fastest possible optimization we can do, but it is not done yet. Some benchmarking would be appreciated.
Is your feature request related to a problem? Please describe.
I'm always frustrated when metabase work nonoptimal.
Describe the solution you'd like
Counters are stored in a single KV pair as a usual concatenation of 8-byte counters. Usually, they are updated in a single transaction one by one.
Describe alternatives you've considered
Keep it as is.
Additional context
Originally posted by @roman-khimov in #3856 (comment)
I am not sure if it is worth it, to be honest. Also, it is not clear whether we need it if #3856 (comment) is not solved, cause this is the fastest possible optimization we can do, but it is not done yet. Some benchmarking would be appreciated.