kube-ovn ipam目前在内存中实现，对照另一个项目来看，内存中ipam确实是性能最好的一种实现方式。
参考: https://github.com/metal-stack/go-ipam
Supported Databases & Performance
| Database | Acquire Child Prefix | Acquire IP | New Prefix | Prefix Overlap | Production-Ready | Geo-Redundant |
|---|---|---|---|---|---|---|
| In-Memory | 106,861/sec | 196,687/sec | 330,578/sec | 248/sec | N | N |
| KeyDB | 777/sec | 975/sec | 2,271/sec | Y | Y | |
| Redis | 773/sec | 958/sec | 2,349/sec | Y | N | |
| MongoDB | 415/sec | 682/sec | 772/sec | Y | Y | |
| Etcd | 258/sec | 368/sec | 533/sec | Y | N | |
| Postgres | 203/sec | 331/sec | 472/sec | Y | N | |
| CockroachDB | 40/sec | 37/sec | 46/sec | Y | Y |
The benchmarks above were performed using:
- cpu: Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz
- postgres:14-alpine
- cockroach:v22.1.0
- redis:7.0-alpine
- keydb:alpine_x86_64_v6.2.2
- etcd:v3.5.4
- mongodb:5.0.9-focal
后续考虑分析下两者的源码，看是否可以更进一步
网友评论