3 ms·
Why Tokyo Cabinet? How quickly can you populate your database locally? Adding 10 billion objects at 300/seconds will take too long.
by oconnor0 17y ago
Why Tokyo Cabinet?
How quickly can you populate your database locally? Adding 10 billion objects at 300/seconds will take too long.
- crad 17y agoIf I read it correctly, 300 records per second was his production rate. I've benched TokyoCabinet out to be much, much faster.
- mahmud 17y ago1 million records in 0.4 seconds. 2.5M queries per second. http://www.scribd.com/doc/12016121/Tokyo-Cabinet-and-Tokyo-Tyrant-Presentation http://www.scribd.com/doc/12016121/Tokyo-Cabinet-and-Tokyo-T... page 4.
- ntoshev 17y agoYou realize these numbers are not for transactional (ACID) updates, right? They are with write cache enabled, meaning a power failure would cause data reported as written not to be available. I hope it doesn't mean data corruption, if someone has tested this I'd like to hear from them. For ACID storage, one transaction per disk rotation is pretty much a theoretical limit for sustained performance.
- anamax 17y ago> For ACID storage, one transaction per disk rotation is pretty much a theoretical limit for sustained performance. Why? There's nothing about "all or nothing" that forbids performing independent application-level commits with a single implementation-level commit. And, it's even possible to do application-level-dependent commits at the same time. (Yes, it's tricky.) And, you can have commits on different spindles. And, you can do multiple writes during a single rotation.
- leej 17y agoThose numbers are probably from non-real world benchmark tests of sequential read/write. You probably never reach to those levels and when put TT to the equation # will decrease even more.