Windows的MS Velocity与Memcached? [英] MS Velocity vs Memcached for Windows?

问题描述

我一直在关注Microsoft近期对Velocity的推广，它是一种分布式缓存解决方案，可以与Memcached之类的产品竞争.

I've been paying some attention to Microsoft's fairly recent promoting of Velocity as a distributed caching solution that would compete with the likes of Memcached.

一段时间以来，我一直在寻找适用于Windows的64位版本的Memcached 运气不好，而且由于我正在研究的ASP.Net MVC项目的所有内容都是64位的，因此仅使用64位就没有任何意义.

I've been looking for a 64bit version of Memcached for Windows for some time now with no luck, and since everything about the ASP.Net MVC project I'm working on is 64bit, it doesn't make sense to use anything but 64bit.

现在，我们已经使用Beta版中的ASP.NET MVC(希望很快就会出现对冲)押注我们的赌注，但是StackOverflow的表现似乎还不错，所以我对此的关注有限.但是Velocity仍然是一个未知数，并且仍然会是Beta(或CTP)的年龄-但它确实有64位！

Now we're already hedging our bets with ASP.NET MVC in Beta (RTM soon hopefully), but StackOverflow doesn't seem to be doing too badly, so I have limited concerns there. But Velocity is still very much an unknown quantity and will still be Beta (or CTP) for ages - but it does have 64bit!

在这种情况下，有没有人提供相关经验或观点?我们应该为Velocity花些时间吗-甚至在足够接近的地方可以与像Memcached这样的巨头竞争吗?还是我们应该花时间尝试使64位版本的Memcached继续运行?

Does anyone have relevant experience or point of view to offer in this situation? Should we bide our time for Velocity - is it even anywhere near good enough to compete with a giant like Memcached, or should we invest time trying to get a 64bit version of Memcached going?

推荐答案

我们最近对Velocity和Memcached进行了大量比较.简而言之，我们发现Velocity比Memcached慢3倍-5倍，并且(更重要的是)它目前不支持多获取操作.因此，目前，我建议您使用Memcached.另外，我们学到的另一个教训是，分布式缓存中最慢的操作是序列化和反序列化(至少在ASP.NET中).进程内ASP.NET缓存要快几个数量级.因此，您必须更加谨慎地选择缓存策略.

We have done recently a fair amount of comparing of Velocity and Memcached. In the nutshell, we found Velocity to be 3x - 5x slower than Memcached, and (even more crucially) it does not have currently support for a multi-get operation. So at the moment, I would recommend going with Memcached. Also, another lesson we have learned was that the slowest operation in distributed caching is serialization and deserialization (at least in ASP.NET). The in-process ASP.NET cache is order of magnitudes faster. So you have to choose caching strategies much more carefully.

这篇关于Windows的MS Velocity与Memcached?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！