etcd-io/etcd
Ver no GitHubOptimize Range WithKeysOnly to avoid loading values in memory
Open
#20.386 aberto em 22 de jul. de 2025
area/performancehelp wantedpriority/important-longtermstage/triagedtype/feature
Métricas do repositório
- Stars
- (51.701 stars)
- Métricas de merge de PR
- (Mesclagem média 6d 3h) (71 fundiu PRs em 30d)
Description
What would you like to be added?
Kubernetes 1.34 will start using Range WithKeysOnly. Main reason to use this method is to reduce the overhead of loading values in memory when they are not needed. While using WithKeysOnly avoids transferring them to client, it doesn't help with etcd memory
Noticed that it loads values in memory just to throw them out little later: https://github.com/etcd-io/etcd/blob/810d69619e33aa09bfdc0449dc65ceb34e589ab6/server/etcdserver/txn/range.go#L150-L152
TODO:
- Add thorough tests for range so we don't break it.
- Identify places that use value in etcd server. For example when sorting by value
- Implement support for KeysOnly method for keyindex
- Use KeysOnly method when we don't need value, like when we don't sort by it.
- Benchmark to show improvement
Please note this task is complicated and not good for first contributor.
Why is this needed?
Align with user expectation that using WithKeysOnly is more efficient on server.