| Cute website. Some random thoughts: Concurrency: - No mention of it. There appear to be spin locks in the source. No multi-threaded tests. Stability and data safety: - Github has 2 days of history, and 4kLoC of test code. Why should I trust my data to you? "high load environment": - So what exactly does it do in a "high load environment"? How do you define "high load" in the first place? CPU load? I/O load from other processes? What shortcomings of the competition under a "high load environment" are you trying overcome? Backup: - How do I do hot backup? Benchmark: - LevelDB is not a fair comparison as it offers additional non-trivial functionality (snapshots) that cannot be built up on top of Sophia. LevelDB APIs are also safe for concurrent use, which adds overhead. Kyoto Cabinet would have been more suitable as a peer to benchmark with. - 3 million records with 16-byte keys and 100-byte values is not really an interesting benchmark dataset. - Iteration over a static database is not interesting, either. Is there any alternative other than locking an entire mutating database for the duration of iteration? |