Memcached and Redis Performance test summary

Memcached and Redis Performance test summary

– The same data model, memcached can save more heat data than redis, such as memcached in 13G of limited memory can save 100 million data, and Redis probably saved 80 million

– the same server environment, memcached write performance is higher than Redis, the former about 100,000 per second, the latter about 70,000 seconds

– When the memory limit is reached, the memcached insertion performance is somewhat jitter at the critical point, probably down to 70,000 per second, after performance is the same as before the critical point, and redis performance drops sharply, once down to 396 per second, The performance is degraded by the sub-process dump data and the large number of page faults per second produced by 栺.

–memcached average consumption of a single CPU percentage, in addition to the memory limit of 300%, the other has been stable around 150%, Redis before reaching the memory limit has been stable at around 90%, and then by the child process dump data and 栺 per second produced a large number of page errors affected, CPU usage is not high, once dropped to 1%

–redis single-threaded operation with low CPU utilization, it is recommended to deploy multiple Redis on the same machine to improve CPU utilization

– Both memory consumption increases as the write data grows, where memcached no longer changes when the memory limit is reached, and the Redis memory footprint is continuously degraded by the sub-process dump data competition

–memcached because it is pure memory operation, so there is no production 栺 page error, and Redis after reaching the upper memory limit, due to the need to transfer part of the data to virtual memory, and then by its sub-process dump data Competition system resources impact will produce 栺 a large number of page errors

– the same server environment, memcached read performance is higher than Redis, the former about 100,000 per second, the latter about 80,000 seconds

– When the memory limit is reached, the memcached read performance does not change, and redis performance drops sharply, once down to 1,100 per second, and its performance is highly unstable by the sub-process dump data and the 栺 of a large number of page faults per second

From the test, Redis is not the king of performance, but its performance is still very strong, for most of the performance requirements are fully satisfied, but its function of the perfect degree, can win over memcached, easier business support, lower development costs

This article is from "Effort!" Struggle! "Blog, be sure to keep this provenance http://026mm.blog.51cto.com/8783374/1775763

Memcached and Redis Performance test summary