I have varying levels of familiarity with Google’s original leveldb and three of its derivatives. RocksDB is one of the three. In each of the four leveldb offerings, the code is optimized for a given environment. Google’s leveldb is optimized for a cell phone, which has much more limited resources than a server. RocksDB is optimized for flash arrays on a large servers (per various Rocksdb wiki pages). Note that a flash array is a device of much higher throughput than a SATA or SSD drive or array. It is a device that sits on the processor’s bus. RocksDB’s performance benchmark page details a server with 24 logical CPU cores, 144GB ram, and two FusionIO flash PCI devices. Each FusionIO device cost about $10,000 at the time of the post. So RocksDB is naturally tuned for extremely fast and expensive systems. Here is an example Arangodb import on a machine similar to the RocksDB performance tester: Read more
- Why ArangoDB?
- Performance
- Docs
- Learn
- White Papers
- What is a multi-model database
- Coming from Relational
- Resilience in ArangoDB 3
- Cluster Performance
- ArangoSearch Tutorial
- Graph Course
- Cluster Course
- Performance Course
- Spring Data
- ArangoDB CRUD
- ArangoDB in 10 Minutes: Node.js
- MongoDB to ArangoDB Tutorial
- Tutorial: PHP in 10 minutes
- Tutorial: ArangoDB with Python
- Tutorial Sync Java Driver
- Foxx Fine-Grained Permissions
- Fault-tolerant Foxx
- User Management
- Geo Index Cursor
- Pregel
- SmartGraphs
- Smatifier
- Cytoscape
- Using collectd, Prometheus & Grafana
- Community
- Subscriptions
- Blog
- Download