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

This article mainly introduces "what are the performance testing methods of Ignite and Hazelcast". In the daily operation, I believe that many people have doubts about what the performance testing methods of Ignite and Hazelcast are. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts of "what are the performance testing methods of Ignite and Hazelcast?" Next, please follow the editor to study!

Performance comparison between Ignite and Hazelcast

Performance tests are based on Ignite 1.5.0-b1 and Hazelcast 3.6-EA2 versions, and evaluate and compare the performance of their various atomized and transactional cache operations and SQL-based cache queries. The results obtained include throughput, latency and various metrics measured during benchmark execution.

Hardware environment configuration

The hardware environment is based on AWS EC2 and is configured as follows:

Hardware c4.2*largeCPU8RAM16GibOSUbuntu 14.04

Yardstick configuration

Node 1 client, 4 server thread 64 backup 1, synchronous mode JDKJava 1.7.0transactions without deadlock transactions (optimistic, serialized)

Hazelcast does not support deadlock-free transactions, so it only compares Ignite's deadlock-free transactions with Hazelcast's pessimistic transactions.

Put benchmark test

Throughput (operations / second). The higher the number, the better the throughput.

Number of keys IgniteHazelcast advantage 166, 53437, 06979, 230, 52316, 62083, 615, 778, 61183, 1012, 6515871115.

Delay (milliseconds). The lower the value, the lower the delay.

Number of keys IgniteHazelcast10.961.7322.093.8564.057.43105.0610.90

For more information, please refer to: 1 key, 2 keys, 6 keys, 10 keys

Put and Get benchmark

Throughput (operations / second). The higher the number, the better the throughput.

Number of keys IgniteHazelcast advantage: 127, 18516, 42565% 223, 44014, 0226, 612, 9006, 70792, 1010, 0614, 396128.

Delay (milliseconds). The lower the value, the lower the delay.

Number of keys IgniteHazelcast12.353.8922.814.5764.969.57106.3614.61

For more information, please refer to: 1 key, 2 keys, 6 keys, 10 keys

Transactional operation

Put benchmark test

Throughput (operations / second). The higher the number, the better the throughput.

Number of keys IgniteHazelcast advantage 146magistrate 3103meme 06924% 226pr 56216pr 62059% 611pr 4658pr 61133% 107pr 8665jr 87134%

Delay (milliseconds). The lower the value, the lower the delay.

Number of keys IgniteHazelcast11.381.7322.413.8565.587.43108.1410.90

For more information, please refer to: 1 key, 2 keys, 6 keys, 10 keys

Pessimistic Put and Get benchmarks

Throughput (operations / second). The higher the number, the better the throughput.

Number of keys IgniteHazelcast advantage 121pc05416meme 42528% 221pr 76814pr 02255% 610pr 7146pr 70759% 107pr 5344pr 39671%

Delay (milliseconds). The lower the value, the lower the delay.

Number of keys IgniteHazelcast13.043.8922.944.5765.979.57108.5014.61

For more information, please refer to: 1 key, 2 keys, 6 keys, 10 keys

Optimistic Put and Get benchmarks

Throughput (operations / second). The higher the number, the better the throughput.

Number of keys IgniteHazelcast advantage 144pc92227pr 40463% 221pr 38012pr 85466% 69pr 7635pr 84367% 106pr 9643m 78484%

Delay (milliseconds). The lower the value, the lower the delay.

Number of keys IgniteHazelcast11.422.3422.994.9866.6010.96109.1916.94

For more information, please refer to: 1 key, 2 keys, 6 keys, 10 keys

Atomization operation

Put benchmark test

Throughput (operations / second). The higher the number, the better the throughput.

Number of keys IgniteHazelcast advantage 111406398 IgniteHazelcast 59715% 287 287 6277 75212% 660 38049 42222% 1050 5833643738%

Delay (milliseconds). The lower the value, the lower the delay.

Number of keys IgniteHazelcast10.560.6420.720.8261.01.2101.21.7

For more information, please refer to: 1 key, 2 keys, 6 keys, 10 keys

SQL query benchmark

Throughput (operations / second). The higher the number, the better the throughput.

Project IgniteHazelcast advantage SQL query 76Get 59653GI 76542% SQL query Put64,15658,32310%

Delay (milliseconds). The lower the value, the lower the delay.

The number of keys IgniteHazelcast10.831.1820.991.09 so far, on the "Ignite and Hazelcast performance testing method is what" the end of the study, I hope to be able to solve everyone's doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

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.