Voldemort如何与Cassandra比较？ [英] How does Voldemort compare to Cassandra?
问题描述
我不是说社区的规模，只想听到
I'm not talking about size of community and only want to hear from people who have actually used both.
特别感兴趣的是：
- 添加和删除节点时的规模。
- 查询效果
- 添加节点>写入速度
推荐答案
Voldemort最近刚刚添加了对节点的支持。因此，考虑到更长的烹饪时间和更大的社区测试，我预计Cassandra会更加健壮。
Voldemort's support for adding nodes was just added recently (this month). So I would expect Cassandra's to be more robust given the longer time to cook and a larger community testing.
两者都是快速的（每台机器大于10k ops / s）。由于它们的存储设计，我希望Cassandra在写入时更快，Voldemort在读取时更快。我也预计Cassandra的性能会随着每个节点的数据量的增加而降低。当然，如果你需要的不仅仅是一个键/值数据模型Cassandra的ColumnFamily模型获胜。
Both are fast (> 10k ops/s per machine). Because of their storage designs, I would expect Cassandra to be faster at writes, and Voldemort to be faster at reads. I would also expect Cassandra's performance to degrade less as the amount of data per node increases. And of course if you need more than just a key/value data model Cassandra's ColumnFamily model wins.
我不知道任何头对头的基准，因为一个去年6月为NoSQL SF做了一个，发现Cassandra在他使用的任何工作负载组合中都要快些。 （来自 http://blog.oskarsson.nu/2009的vpork演讲/06/nosql-debrief.html ）8个月是一个永恒的项目在这个发展，虽然。
I don't know of any head-to-head benchmarks since the one done for NoSQL SF last June, which found Cassandra to be somewhat faster at whatever workload mix he was using. (The "vpork" talk from http://blog.oskarsson.nu/2009/06/nosql-debrief.html) 8 months is an eternity with projects under this much development, though.
这篇关于Voldemort如何与Cassandra比较？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
