伏地魔与卡桑德拉相比如何？
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.
Especially I'm interested in:
- How they dynamically scale when adding and removing nodes
- Query performance
- How they scale when adding nodes (linear)?
- Write speed
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Voldemort 最近（本月）刚刚添加了对添加节点的支持。因此，考虑到更长的烹饪时间和更大的社区测试，我预计 Cassandra 会更加强大。
两者都很快（每台机器 > 10k ops/s）。由于它们的存储设计，我希望 Cassandra 的写入速度更快，而 Voldemort 的读取速度更快。我还预计随着每个节点数据量的增加，Cassandra 的性能下降得更少。当然，如果您需要的不仅仅是键/值数据模型，Cassandra 的 ColumnFamily 模型会胜出。
自去年 6 月针对 NoSQL SF 进行的基准测试以来，我不知道有任何面对面的基准测试，该基准测试发现 Cassandra 在他使用的任何工作负载组合上都更快。 （“vpork”演讲来自 http://blog.oskarsson.nu/2009/ 06/nosql-debrief.html）不过，对于如此大规模开发的项目来说，8 个月是一个永恒的时间。
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.
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.
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 可以提供范围查询（使用保留顺序的分区器），以及围绕数据的更多结构（列族等）。前者是设计的重要考虑因素；后者在我看来不太如此，您始终可以在客户端构建 BLOB 数据。
Some additional comments:
But main difference I think is actually not performance but feature set: Voldemort is strictly a key/value store (currently anyway), whereas Cassandra can offer range queries (with order-preserving partitioner), and bit more structure around data (column families etc). Former is an important consideration for design; latter IMO less so, you can always structure BLOB data on client side.