您使用哪个 .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 库.两者都是正在开发中的相当活跃的项目，下载量超过一千次.试图弄清楚该使用哪个，但发现了相互竞争的言论！我确实阅读了另一个相关的帖子，但仍然想在做出决定之前询问更多人.

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://code.google.com/p/beitmemcached/wiki/Features)

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

我们已经对 BeIT Memcached 客户端进行了广泛的功能测试和性能测试，我们对其正常工作感到满意.当我们将性能与其他两个客户端(java 端口和 Enyim memcached 客户端)进行比较时，我们的客户端消耗了资源最少，性能最好.它也更严格地遵循memcached协议规范，拥有最多的memcached特性，实际代码量仍然小得多.

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 客户端.

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屋！