伏地魔与卡桑德拉相比如何? [英] How does Voldemort compare to Cassandra?

问题描述

Voldemort 与 卡桑德拉?

我不是在谈论社区的规模，只是想听听实际使用过两者的人的意见.

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/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.

这篇关于伏地魔与卡桑德拉相比如何?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！