CODIS long link test

background ：2022-2-10 Day client cpu The load goes up , codis proxy The load on the host is also increasing

Testing tools ：memtier_benchmark

redis Pressure measuring tool : https://github.com/RedisLabs/memtier_benchmark/archive/refs/heads/master.zipredis Pressure measuring tool : 

1.  single proxy test （ A long connection ） Same as segment

proxy To configure   (max cpu32、maxclient 100000   、offheap maxmemory 1024mb)

Installation tutorial ： Use memtier_benchmark Tools for performance testing _ Distributed cache service DCS_ Performance white paper _ The test method _ Hua Wei Yun

Parameter description ：

-n： Operands

-d:  The size of the data used for the test Company byte

-c： Number of simulated clients

-t： Number of threads ( Default not specified as 4c)

2.  single proxy test （ A long connection ） Same as segment

proxy To configure   (max cpu32、maxclient 100000   、offheap maxmemory 1024mb)

The number of connections	command	qps	client
500	memtier_benchmark -s 10.138.20.97 -p 19000 -n 10000000 -d 64 -c 125	18W about	1
1000	memtier_benchmark -s 10.138.20.97 -p 19000 -n 10000000 -d 64 -c 250	22W+	1
2000	memtier_benchmark -s 10.138.20.97 -p 19000 -n 10000000 -d 64 -c 500	20W+	1
6000	memtier_benchmark -s 10.138.20.97 -p 19000 -n 10000000 -d 64 -c 1500	16W+	1
8000	memtier_benchmark -s 10.138.20.97 -p 19000 -n 10000000 -d 64 -c 2000	14W ～16W	1
10000	memtier_benchmark -s 10.138.20.97 -p 19000 -n 10000000 -d 64 -c 2500	12W+	1
20000	memtier_benchmark -s 10.138.20.97 -p 19000 -n 10000000 -d 64 -c 5000	4W	1
40000	memtier_benchmark -s 10.138.20.97 -p 19000 -n 10000000 -d 64 -c 10000	2W～3W	1
40000	memtier_benchmark -s 10.138.20.97 -p 19000 -n 10000000 -d 64 -c 1000 -t 4	14.5	10

Conclusion ： Test a single with long links proxy, The number of connections is 1000 - 2000 proxy The highest performance , The number of connections is too low and the concurrency is low qps low

codis-proxy Distribute request traffic to codis-server Long link
codis-server Master and slave synchronize data with each other Long link

3. many proxy test （ A long connection ） Same as segment

The phenomenon ： Two sets of client The server starts four processes , Each process starts two threads . Visit each of the four proxy, Results found proxy Of qps It can only reach 4W-5W about . Test access to a single machine proxy, Starting a process can achieve

Knowledge point ：codis-proxy Will send it regularly ping package , Check codis server Whether it is alive

Test method ： 8 platform client At the same time establish 8 Processes to access 8 individual proxy

explain ： 10 One test client To visit 8 individual proxy  Every test client Turn on 3 A process   simulation 133 Multiple clients access at the same time proxy

The number of connections	command	qps	proxy	client
500	memtier_benchmark -s $element -p 19000 -n 200000 -d 64 -c 21 -t 3	20W*8	8	8
1000	memtier_benchmark -s $element -p 19000 -n 200000 -d 64 -c 42 -t 3	20W*8	8	8
2000	memtier_benchmark -s $element -p 19000 -n 200000 -d 64 -c 84 -t 3	21W*8	8	8
4000	memtier_benchmark -s $element -p 19000 -n 200000 -d 64 -c 133 -t 3	18W*8	8	10
6000	memtier_benchmark -s 10.138.20.97 -p 19000 -n 10000000 -d 200 -c 1500	17W+*8	8	8
8000	memtier_benchmark -s 10.138.20.97 -p 19000 -n 10000000 -d 267 -c 2000	15.5W*8	8	8
10000	memtier_benchmark -s 10.138.20.97 -p 19000 -n 10000000 -d 334 -c 2500	15.5W*8	8	8
20000	memtier_benchmark -s 10.138.20.97 -p 19000 -n 10000000 -d 667 -c 5000	14.75W*8	8	8
40000	memtier_benchmark -s 10.138.20.97 -p 19000 -n 10000000 -d 64 -c 10000	14W*8	8	8

summary ： Use multiple test machines, each starting 8 Test scripts are accessed separately 8 individual proxy, The number of connections is less than 4000 Under the circumstances , Single proxy Of qps The maximum can reach each 20W about , When the number of connections reaches 40000 The situation of proxy qps Stay in 14W about .