Open the Redis-Server web console. We will restart our redis server before our next test. Change the directory to the scripts folder if you aren’t already there.
Execute the following scripts. Once the scripts have been executed, you will see the Redis process running.
launchpad@Redis-Server:~/Scripts$ ./stopRedis.sh Stoping Redis Server... Done launchpad@Redis-Server:~/Scripts$ ./startRedis.sh Starting Redis server... root 1853 1 0 21:12 ? 00:00:00 redis-server 0.0.0.0:5000 Done
Next, you will make sure that the server is responsive by executing a ping command.
launchpad@Redis-Server:~/Scripts$ redis-cli -p 5000 127.0.0.1:5000> ping PONG 127.0.0.1:5000> exit launchpad@Redis-Server:~/Scripts$
We are done configuring the Redis-Server. Next, we will move to the Benchmark-Client.
Let’s first run a sanity check to see that the redis server is accessible from the client. We can run the same command as above but now pass the host parameter along with the port.
Enter the command shown below. The UPT test will run over the 10.X.X.X network using a DPU-offloaded NSX vSwitch.
launchpad@Benchmark-Client:~$ redis-cli -h 10.10.10.10 -p 5000 10.10.10.10:5000> ping PONG 10.10.10.10:5000> exit launchpad@Benchmark-Client:~$
Next, we will be running the memtier benchmark. The
runPerfTest-UPT.shscript runs memtier with pre-assigned parameters and collects performance metrics in/home/launchpad/Results/results.txt. The script first runs a redis server warmup and then 5 iterations of performance benchmarking. This test should take a few minutes to run.launchpad@Benchmark-Client:~/Scripts$ ./runPerfTest-UPT.sh Writing results to ../Results/UPT-2023.02.03-23.07.03/warmup-run-.txt... [RUN #1] Preparing benchmark client... [RUN #1] Launching threads now... ... [RUN #1 100%, 60 secs] 0 threads: 11041746 ops, 186246 (avg: 184027) ops/sec, 22.18MB/sec (avg: 21.92MB/sec), 0.16 (avg: 0.16) msec latency 2023.02.03-23.08.03 Starting iteration.. 1 Writing results to ../Results/UPT-2023.02.03-23.07.03/results-run-1.txt... [RUN #1] Preparing benchmark client... [RUN #1] Launching threads now... ... [RUN #1 100%, 30 secs] 0 threads: 25463220 ops, 855095 (avg: 848762) ops/sec, 98.15MB/sec (avg: 97.40MB/sec), 0.17 (avg: 0.18) msec latency 2023.02.03-23.08.43 Starting iteration.. 2 Writing results to ../Results/UPT-2023.02.03-23.07.03/results-run-2.txt... [RUN #1] Preparing benchmark client... [RUN #1] Launching threads now... ... [RUN #1 100%, 30 secs] 0 threads: 24642460 ops, 866058 (avg: 821405) ops/sec, 99.39MB/sec (avg: 94.26MB/sec), 0.17 (avg: 0.18) msec latency 2023.02.03-23.09.23 Starting iteration.. 3 Writing results to ../Results/UPT-2023.02.03-23.07.03/results-run-3.txt... [RUN #1] Preparing benchmark client... [RUN #1] Launching threads now... ... [RUN #1 100%, 30 secs] 0 threads: 25454360 ops, 856019 (avg: 848469) ops/sec, 98.22MB/sec (avg: 97.37MB/sec), 0.17 (avg: 0.18) msec latency 2023.02.03-23.10.03 Starting iteration.. 4 Writing results to ../Results/UPT-2023.02.03-23.07.03/results-run-4.txt... [RUN #1] Preparing benchmark client... [RUN #1] Launching threads now... ... [RUN #1 100%, 30 secs] 0 threads: 25029220 ops, 865059 (avg: 834297) ops/sec, 99.29MB/sec (avg: 95.74MB/sec), 0.17 (avg: 0.18) msec latency 2023.02.03-23.10.43 Starting iteration.. 5 Writing results to ../Results/UPT-2023.02.03-23.07.03/results-run-5.txt... [RUN #1] Preparing benchmark client... [RUN #1] Launching threads now... ... [RUN #1 100%, 30 secs] 0 threads: 24630055 ops, 805309 (avg: 820991) ops/sec, 92.42MB/sec (avg: 94.22MB/sec), 0.19 (avg: 0.18) msec latency
Now let’s take a look at the results of the test. In the next step we will compare results.
launchpad@Benchmark-Client:~$ cat ~/Results/results.txt UPT-2023.02.03-23.07.03 Summary: Total Iterations:5 Operations/Sec: 846947 Latency: 0.179008 ms Bandwidth: 99.5284 Mb/s