{"id":135788,"date":"2025-06-04T09:05:06","date_gmt":"2025-06-04T07:05:08","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/sravnenie-proizvoditelnosti-subd-valkey-i-redis"},"modified":"2025-06-04T09:05:06","modified_gmt":"2025-06-04T07:05:08","slug":"sravnenie-proizvoditelnosti-subd-valkey-i-redis","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/sravnenie-proizvoditelnosti-subd-valkey-i-redis","title":{"rendered":"Comparison of Valkey and Redis DBMS Performance","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The results of testing the fresh releases of the Redis 8.0 and Valkey 8.1 databases are presented, which have announced significant performance optimizations. In all conducted tests, the community-driven fork surpassed the original project, mainly due to the implementation of a new mechanism for multi-threaded asynchronous input\/output processing, provided to the project by Amazon. <\/p>\n
In the AWS Graviton4 test environment c8g.2xlarge with 8 VCPUs, Valkey 8.1.1 achieved a performance of 999.8 thousand SET requests per second, while Redis 8.0 reached a level of 729.4 thousand requests per second. Overall, Valkey's throughput was 37% higher than Redis for SET operations and 16% for GET. Additionally, compared to Redis, the Valkey project demonstrated a 30% reduction in latency for SET operation requests and a 60% reduction for GET operations.
<\/center> <\/p>\n
A separate analysis was conducted on the changes in bandwidth and latency depending on the number of concurrently running handlers in multithreaded I\/O processing mode. Up to 3 threads, Valkey and Redis show roughly equal results, but then Valkey pulls ahead. With 6 threads on a system with 8 VCPUs, Valkey's performance reached 678,000 SET requests per second, while Redis achieved 563,000 requests per second with a limit of 256 simultaneous connections. When connections were increased to 400, Valkey's performance grew to 832,000 SET requests per second.
<\/center> <\/p>\n
After optimizing interrupt handling in the system to reduce context switching, Valkey's performance was boosted to 999.8 thousand SET requests per second. The essence of the optimization involved allocating 2 VCPUs for interrupt handling and binding the remaining 6 VCPUs to the I\/O processing threads of Valkey and Redis to prevent handler migration between CPUs. sudo ethtool -L ens34 combined 2 # limit the number of IRQ handlers to 2 grep ens34 \/proc\/interrupts # check which handlers are active (99 and 100) echo 1 | sudo tee \/proc\/irq\/99\/smp_affinity # bind handler 99 to core 1 echo 2 | sudo tee \/proc\/irq\/100\/smp_affinity # bind handler 100 to core 2 # Start the DB (for Redis, change valkey\/valkey:8.1.1 to redis:8.0) with the container bound to CPU cores 2-7 docker run --network='host' --rm \\ --cpuset-cpus='2-7' valkey\/valkey:8.1.1 \\ --save 'no' --appendonly no --io-threads 6 \\ --protected-mode no --maxmemory 10gb <\/p>\n
![\"Comparison](\"\/wp-content\/uploads\/2025\/06\/512bd8dc9f4e4cc2562b59db68823b07.png\")
<\/center> <\/p>\n![\"Comparison](\"\/wp-content\/uploads\/2025\/06\/b81d26ec066d0af829859a11236ae2a6.png\")
<\/center> <\/p>\n