**【环境信息】**

双端物理机，并在其中一个物理机上创建ovs+dpdk组网的2个vm

openeulerversion=openEuler-22.03-LTS-SP2

compiletime=2023-06-29-19-26-48

gccversion=10.3.1-37.oe2203sp2

kernelversion=5.10.0-153.12.0.92.oe2203sp2

openjdkversion=1.8.0.372.b07-1.oe2203sp2

[root@openEuler mysql]# rpm -q gazelle

gazelle-1.0.2-9.krpc.aarch64

[root@openEuler ~]# rpm -q dpdk

dpdk-21.11-50.oe2203sp2.aarch64

**【问题复现步骤】**，请描述具体的操作步骤

主从redis分别在不同的vm中，主从配置基本一致，在从的redis.conf中开启appendonly yes

在vm端，启动主redis-server LD_PRELOAD=/usr/lib64/liblstack.so GAZELLE_BIND_PROCNAME=redis-server /root/redis-server ${redis_conf}

gazelle配置如下

```

dpdk_args=["--socket-mem", "2000,0,0,0", "--huge-dir", "/mnt/hugepages-lstack", "--proc-type", "primary", "--legacy-mem", "--map-perfect"]

use_ltran=0

kni_switch=0

low_power_mode=0

#needed mbuf count = tcp_conn_count * mbuf_count_per_conn

tcp_conn_count=1500

mbuf_count_per_conn=138

# send ring size, default is 32, max is 2048

send_ring_size = 32

# 0: when send ring full, send return

# 1: when send ring full, alloc mbuf from mempool to send data

expand_send_ring = 0

#protocol stack thread per loop params

#read data form protocol stack into recv_ring

read_connect_number = 4

#process rpc msg number

rpc_number = 4

#read nic pkts number

nic_read_number = 128

#each cpu core start a protocol stack thread.

num_cpus="1"

#app worker thread bind to numa in epoll/poll.

app_bind_numa=1

#app main thread affinity set by dpdk.

main_thread_affinity=0

host_addr="124.88.40.151"

mask_addr="255.255.0.0"

gateway_addr="124.88.0.1"

devices="52:54:00:c8:03:f9"

#0: use rss rule

#1: use tcp tuple rule to specify packet to nic queue

tuple_filter=0

#tuple_filter=1, below cfg valid

num_process=1

process_numa="0,1"

process_idx=0

#tuple_filer=0, below cfg valid

listen_shadow=0

udp_enable=0

```

在另一个vm端，启动从redis-server LD_PRELOAD=/usr/lib64/liblstack.so GAZELLE_BIND_PROCNAME=redis-server /root/redis-server ${redis_conf}

gazelle配置如下

```

dpdk_args=["--socket-mem", "2000,0,0,0", "--huge-dir", "/mnt/hugepages-lstack", "--proc-type", "primary", "--legacy-mem", "--map-perfect"]

use_ltran=0

kni_switch=0

low_power_mode=0

#needed mbuf count = tcp_conn_count * mbuf_count_per_conn

tcp_conn_count=1500

mbuf_count_per_conn=138

# send ring size, default is 32, max is 2048

send_ring_size = 32

# 0: when send ring full, send return

# 1: when send ring full, alloc mbuf from mempool to send data

expand_send_ring = 0

#protocol stack thread per loop params

#read data form protocol stack into recv_ring

read_connect_number = 4

#process rpc msg number

rpc_number = 4

#read nic pkts number

nic_read_number = 128

#each cpu core start a protocol stack thread.

num_cpus="1"

#app worker thread bind to numa in epoll/poll.

app_bind_numa=1

#app main thread affinity set by dpdk.

main_thread_affinity=0

host_addr="124.88.8.55"

mask_addr="255.255.0.0"

gateway_addr="124.88.0.1"

devices="52:54:00:f9:d2:68"

#0: use rss rule

#1: use tcp tuple rule to specify packet to nic queue

tuple_filter=0

#tuple_filter=1, below cfg valid

num_process=1

process_numa="0,1"

process_idx=0

#tuple_filer=0, below cfg valid

listen_shadow=0

udp_enable=0

```

在物理机客户端依次测试如下命令


**【实际结果】**，请描述出问题的结果和影响

测试set时相对单机性能下降明显，内核态在包长3连接1000时无此问题


双端物理机，并在其中一个物理机上创建ovs+dpdk组网的2个vm

主从redis分别在不同的vm中，主从配置基本一致，在从的redis.conf中开启appendonly yes 开启cluster-enabled yes

gazelle配置如下，其余vm配置参照这个配置修改mac地址和ip

通过客户端创建集群

redis-cli --cluster create ip1:port1 ip2:port2 ip3:port3 ip4:port4 ip5:port5 ip6:port6 --cluster-replicas 1

检查集群状态，确认ok

redis-cli -h ${vm_sip1} -p 6379 -e 'cluster info'

开始进行测试（先测试set再测试get，测试完一轮之后需要清空数据库或者重启redis-server）

./redis-benchmark -h 192.168.33.33 -p 6379 -c 1000 -n 10000000 -r 100000 -t set --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 1000 -n 10000000 -r 10000000 -t get --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 1000 -n 10000000 -r 100000 -t set --threads 12 --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 1000 -n 10000000 -r 10000000 -t get --threads 12 --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 1000 -n 10000000 -r 100000 -t set --threads 20 --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 1000 -n 10000000 -r 10000000 -t get --threads 20 --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 1000 -n 10000000 -r 100000 -t set -d 1024 --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 1000 -n 10000000 -r 10000000 -t get -d 1024 --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 1000 -n 10000000 -r 100000 -t set -d 1024 --threads 12 --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 1000 -n 10000000 -r 10000000 -t get -d 1024 --threads 12 --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 1000 -n 10000000 -r 100000 -t set -d 1024 --threads 20 --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 1000 -n 10000000 -r 10000000 -t get -d 1024 --threads 20 --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 5000 -n 10000000 -r 100000 -t set --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 5000 -n 10000000 -r 10000000 -t get --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 5000 -n 10000000 -r 100000 -t set --threads 12 --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 5000 -n 10000000 -r 10000000 -t get --threads 12 --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 5000 -n 10000000 -r 100000 -t set --threads 20 --cluster

./redis-benchmark -h 192.168.33.33 -p 6379 -c 5000 -n 10000000 -r 10000000 -t get --threads 20 --cluster

**【实际结果】**，请描述出问题的结果和影响

1000连接场景，set性能差于内核，get性能无明显提升