A better format result: 1KB Block LevelDB with Compress: 1.77MB/s LevelDB without Compress: 1.12MB/s Btrfs: 13.84MB/s 4KB Block LevelDB with Compress: 5.15MB/s LevelDB without Compress: 3.21MB/s Btrfs: 12.96MB/s 8KB Block LevelDB with Compress: 6.44MB/s LevelDB without Compress: 4.57MB/s Btrfs: 18.29MB/s 128KB Block LevelDB with Compress: 7.64MB/s LevelDB without Compress: 7.28MB/s Btrfs: 95.26MB/s 1MB Block LevelDB with Compress: 13.61MB/s LevelDB without Compress: 13.28MB/s Btrfs: 109.23MB/s On 31 July 2013 14:04, 袁冬 <yuandong1222@xxxxxxxxx> wrote: > We have the same idea and already tested the LevelDB Performance VS > Btrfs. The result is negative, especially for big block IO. > > 1KB Block 4KB > Block 8KB Block 128KB Block 1MB Block > LevelDB with Compress: 1.77MB/s 5.15MB/s 6.44MB/s > 7.64MB/s 13.61MB/s > LevelDB without Compress: 1.12MB/s 3.21MB/s 4.57MB/s > 7.28MB/s 13.28MB/s > Btrfs 13.84MB/s > 12.96MB/s 18.29MB/s 95.26MB/s 109.23MB/s > > On 31 July 2013 06:54, Alex Elsayed <eternaleye@xxxxxxxxx> wrote: >> I posted this as a comment on the blueprint, but I figured I'd say it here: >> >> The thing I'd worry about here is that LevelDB's performance (along with >> that of various other K/V stores) falls off a cliff for large values. >> >> Symas (who make LMDB, used by OpenLDAP) did some benchmarking that shows >> drastic performance loss with 100KB values on both read and write: >> http://symas.com/mdb/microbench/#sec4 >> >> It's not just disk latency, either - an SSD showed the same behavior: >> http://symas.com/mdb/microbench/#sec7 >> >> I'd recommend REALLY careful benchmarking with a variety of loads (and value >> sizes). >> >> -- >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > -- > Dong Yuan > Email:yuandong1222@xxxxxxxxx -- Dong Yuan Email:yuandong1222@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
