News for hackers. Stuff that matters.
Re:Databases at 14.4Mhz by misframer on Wednesday December 10, 2014 @03:04PM (#8731340)
> Still. Aside from that, it is free, and open source and gives hundred times better latency?

It doesn't have the same guarantees. If you need those guarantees, then there's no comparison and it doesn't make sense to compare latencies.

Re:Databases at 14.4Mhz by dchichkov on Wednesday December 10, 2014 @03:10PM (#8731375)
I'm not so sure. Have the latencies claimed by FoundationDB been measured on multi-key transactions?

And if you need these guaranties, it seems like "Most of these operations can be implemented on top of the existing RAMCloud features". I would expect it to be possible to implement that and stay well withing the latency budget, provided that a single-key durable write is 100 times faster.

Re:Databases at 14.4Mhz by nlavezzo on Wednesday December 10, 2014 @03:16PM (#8731410)
All of the transactions in the test noted in the blog are multi-key transactions. (20 key updates)
Re:Databases at 14.4Mhz by dchichkov on Wednesday December 10, 2014 @03:32PM (#8731495)
When claiming the 14.4MHz number, is that per 20-key update? Or a single key update in the 20-key update? And what's the latency on the 20-key update?
Re:Databases at 14.4Mhz by itp on Wednesday December 10, 2014 @06:15PM (#8732303)
The writes we are measuring are individual keys, modified atomically in transactions of 20 keys at a time. So this test is doing 14 million writes per second as 720 thousand transactions per second.
Re:Databases at 14.4Mhz by jrallison on Wednesday December 10, 2014 @03:25PM (#8731460)
Multi-key transactions means coordination. Coordination is not cheap. You'll be paying a hefty cost somewhere.