其中.NET的memcached客户端，你用，EnyimMemcached与BeITMemcached？ [英] Which .NET Memcached client do you use, EnyimMemcached vs. BeITMemcached?

问题描述

好像都 EnyimMemcached （ https://github.com/enyim/EnyimMemcached ）和 BeITMemcached （的http：// code.google.com/p/beitmemcached/ ）是流行的.NET Memcached的库。两者都在开发合理活动项目，并有超过一千下载。试图找出哪一个使用但发现竞争的话！我看过其他相关<一个href=\"http://stackoverflow.com/questions/272989/which-memcached-client-library-should-i-use-for-net\">post但仍希望在作出决定之前要求更多的人对这个。

Seems like both EnyimMemcached (https://github.com/enyim/EnyimMemcached) and BeITMemcached (http://code.google.com/p/beitmemcached/) are popular .NET Memcached libraries. Both are reasonably active projects under development and have over a thousand downloads. Trying to figure out which one to use but found competing remarks! I did read another related post but still want to ask more people on this before making a decision.

EnyimMemcached 在其项目主页索赔（ https://github.com/enyim/ EnyimMemcached ），即

EnyimMemcached claims on its project homepage (https://github.com/enyim/EnyimMemcached), that

根据我们的非披露特别手工内部性能测试我们是最快的C＃客户端不断使用的系统资源负数，无论是内存或CPU时间

based on our non-disclosed specially handcrafted in-house performance test we're the fastest C# client ever, using negative amount of system resources, be it memory or CPU time

和

我们遵循memcached的协议规范的严格，因为没有其他人：连memcached的人问我们，如果他们不明白的东西。

we follow memcached's protocol specification as strictly as no one else: even the memcached guys ask us if they don't understand something

在 BeITMemcached 其项目的wiki页面上的债权（的 HTTP：//$c$c.google.com/p/beitmemcached/wiki/Features ）的

While BeITMemcached claims on its project wiki page (http://code.google.com/p/beitmemcached/wiki/Features) that

我们已经进行了广泛的功能测试和贝特哈的Memcached客户端的性能测试，我们satisifed它，它应该工作。当我们比较与其他两个客户端的性能，渣口和 Enyim的memcached客户端，我们的客户所消耗的最少的资源并具有最佳的性能。这也是继memcached的协议规范更严格的，拥有最memcached的功能，并且仍然是实际code尺寸要小得多。

We have performed extensive functional testing and performance testing of the BeIT Memcached client and we are satisifed that it is working as it should. When we compared the performance against two other clients, the java port and the Enyim memcached client, our client consumed the least resources and had the best performance. It is also following the memcached protocol specifications more strictly, has the most memcached features, and is still much smaller in actual code size.

因此​​，对于那些谁对这些或任何类似的经历，你会选择你为什么选择一个你选择？使用和可能的客户端

So for those who have experience on these or anything similar, which client did you choose to use and possibly why you chose the one you chose?

感谢您，

雷。

推荐答案

我们测试都发现Enyim执行最适合我们的预期使用情况：许多（但不是百万）缓存的对象，以及数百万缓存获得请求（平均网站并发负载= 16-20请求。）

We tested both and found Enyim to perform the best for our expected usage scenario: many (but not millions) cached objects, and millions of cache-get requests (average web site concurrency load = 16-20 requests.)

我们的性能因子测量从发出请求到具有主叫服务器上在存储器初始化对象的时间。这两个库将有持续的工作，但enyim客户是在我们的测试pferred $ P $。

Our performance factor was measuring the time from making the request to having the object initialized in memory on the calling server. Both libraries would have sustained the job, but the enyim client was preferred in our testing.

这篇关于其中.NET的memcached客户端，你用，EnyimMemcached与BeITMemcached？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！