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.
特别是我有兴趣:
- 添加和删除节点
- 查询性能
- 添加节点(线性)时如何扩展?
- 速度
- How they dynamically scale when adding and removing nodes
- Query performance
- How they scale when adding nodes (linear)?
- Write speed
推荐答案
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在他使用的任何工作负载组合方面都要快些。 (vpork讲座来自 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.
这篇关于Voldemort如何与Cassandra比较?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!