Closed iomartin closed 1 year ago
hi iomartin, the test script needs to be changed for your platform, it tests on Intel(R) Xeon(R) Platinum 8488C, has 8 QAT devices, we will update this script in next release
Thanks, I'll just change mine to use 12 processes in the meantime. It might also be a good idea to add -B 0
to the test
call as well so that it doesn't silently falls back to software
The process number should match with the NumProcesses in the configuration file, then all the process will use the hardware. In the case, you are using the NumProcesses=6 in the config files and 2 device, so 12 process will use the hardware.
Running the perf_test on a
Intel Xeon Platinum 8480+
, which has 2x 4940 QATs, I see that it tries to start 48 processes. However, I see via htop that 36 cores are at 100% while all others are fairly idle.Furthermore, when I inspect
result_comp
I see that 12 processes achieved "good" compression throughput (5.5-6.3 Gbps), while the other 36 are very slow (~0.5 Gbps):Inspecting
result_comp_stderr
, I see a bunch of messages indicating that it fell back to SW (which explains why 36 cores are at 100%):This seems to be because
NumProcesses = 6
is set in the conf files, as increasing that to 24 makes all processes to run on HW (but then each process is much slower, at about 1.4 Gbps).Does the configuration or the test script needs to be adjusted?