[Reprint] Turn Java several memcached connection client compare Select

Original Address:Turn Java several memcached connection client comparison selection Flash out of the light

Xmemcached 1.2.6.1 Released, so updated Java Memcached Client Benchmark. Compare the performance of the three open source clients under xmemached,spymemcached and java-memcached-client, and the specific test information can be seen in this link.

Test Source:

Java code

1. SVN Co http://xmemcached.googlecode.com/svn/trunk/benchmark/

Test results:

Java code

1. SVN Co http://xmemcached.googlecode.com/svn/trunk/benchmark/result

Summarize the test results and provide references for friends who are still selecting and examining the Java memcached client:

1, java-memcached-client 2.5.1 This version really has a great improvement, the performance of a very large increase, from the test results in less than 100 concurrency has a very obvious advantage, while the cost of resources is relatively more. However, under 300 concurrent accesses, Java-memcached-client will continue to error:

Java code

2. Com.schooner.MemCached.SchoonerSockIOPool Sun Oct 11:09:05 gmt+08:00-++++ failed to get Sockio obj for:10.232.3 6.82:12,000
4. Com.schooner.MemCached.SchoonerSockIOPool Sun Oct 11:09:05 gmt+08:00-++++ failed to get Sockio obj for:10.232.3 6.82:12,000
6. Com.schooner.MemCached.SchoonerSockIOPool Sun Oct 11:09:05 gmt+08:00-++++ failed to get Sockio obj for:10.232.3 6.9:12,000
8. Com.schooner.MemCached.SchoonerSockIOPool Sun Oct 11:09:05 gmt+08:00-++++ failed to get Sockio obj for:10.232.3 6.82:12,000
10. Com.schooner.MemCached.SchoonerSockIOPool Sun Oct 11:09:05 gmt+08:00-++++ failed to get Sockio obj for:10.232.3 6.9:12,000
12. Com.schooner.MemCached.SchoonerSockIOPool Sun Oct 11:09:05 gmt+08:00-++++ failed to get Sockio obj for:10.232.3 6.82:12,000

And the data cannot be accessed properly, while XMC and the spy can handle the scenario normally. So you can see that under 300 concurrency, the results of the Java-memcached-client test are directly 0 because the test cannot be completed. Although I tried to adjust the maximum number of connections to 2000, the test still failed to complete properly.

2, xmemcached in the case of low concurrency or high concurrent access, can maintain a relatively good performance, from the XMC and spy comparison, XMC advantage is quite large.

3, from the user choice point of view, if your application to memached access load is not high, java-memcached-client is a good choice, but in peak access can be a sharp fluctuation in the hit rate If your app accesses memached with high load, I recommend you choose Xmemcached, if you need asynchronous batch processing (future mode), you can choose spymemcached; If you don't know what your app is, I recommend that you use xmemcached to get a better performance in any situation .

[Reprint] Turn Java several memcached connection client compare Select