Shulou(Shulou.com)05/31 Report--

This article mainly introduces the example analysis of memcached and redis performance testing, which is very detailed and has a certain reference value. Interested friends must read it!

Summary of performance Test of memcached and redis

-with the same data model, Memcached can store more hot data than Redis. For example, Memcached can save about 100 million pieces of data in 13 GB of limited memory, while Redis can save about 80 million pieces of data.

-in the same server environment, the write performance of Memcached is higher than that of Redis, with the former about 100000 messages per second and the latter about 70 000 seconds.

-when the memory limit is reached, the Memcached insert performance drops to about 70, 000 entries per second except for some jitter at the critical point, and then the performance is the same as before, while the Redis performance drops sharply to 396 entries per second, and then its performance continues to decline due to the child process dump data and a large number of page errors generated per second.

-Memcached occupies an average percentage of a single CPU, except when the critical point of the memory limit reaches 300%, the other has been stable at about 150%. Before reaching the memory limit, Redis has been stable at about 90%. After that, due to the child process dump data and a large number of page errors generated per second, the CPU utilization rate is not high, once reduced to 1%.

-Redis runs in a single thread, and the utilization of CPU is not high, so it is recommended to deploy multiple redis on the same machine to improve cpu utilization.

-both memory footprint increases with the gradual increase of written data, in which Memcached no longer changes after reaching the memory limit, while Redis memory occupancy continues to decrease due to competition from child process dump data.

-Memcached does not produce page errors because it is a pure memory operation. After reaching the memory limit, Redis will generate a large number of page errors due to the need to transfer part of the data to virtual memory and then be affected by its child process dump data competition for system resources.

-the read performance of Memcached is higher than that of Redis in the same server environment, with the former about 100000 messages per second and the latter about 80 000 seconds.

-when the memory limit is reached, the Memcached read performance does not change, while the Redis performance drops sharply, falling to 1100 entries per second at one point, and then its performance is very unstable due to the child process dump data and a large number of page errors generated per second.

From the test point of view, redis is not the king of performance, but its performance is still very strong, and most of the performance requirements are fully met, but its functional perfection can be better than memcached, business support is easier, and the development cost is lower.

The above is all the content of the article "sample Analysis of memcached and redis performance testing". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.