The performance of the etcd system is complex[1], there’s raft consensus, replication, security, snapshots, networking, and basically a lot going on. Perhaps,

The performance of the etcd system is complex[1], there’s raft consensus, replication, security, snapshots, networking, and basically a lot going on. Perhaps, your benchmarks really do reflect problems that go has with gc, but perhaps some other part amonst the numerous moving parts are causing the poor benchmark results. I’m not sure that we can conclude from your results that go has gc problems when the heap is large. [1] https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/performance.md https://github.com/etcd-io/etcd/blob/master/Documentation/op...