Open phil12ip opened 8 months ago
ACT 5.2 used 4 * <number of cores>
threads for the transaction queues by default.. The equivalent tin 6.4 is the service-threads
which now uses 5* <number of cores>
by default. Could you try manually tuning the number of threads down in 6.4?
I am running ACT benchmark on an NVMe SSD, and seeing odd results between different versions of ACT. Specifically, after act_prep has run, and the drive has reached a steady state, running 40x scaling load via ACT version 5.2 vs. version 6.4 produce very different latency results, running each on the same system and disk. Here is a snippet of the latency results between the two versions. I am using the default config for the specific version in each run, changing only the target
read-reqs-per-sec
andwrite-reqs-per-sec
to match the target load.6.4 ACT Results @40x
5.2 ACT Results @40x
I have attached the full results output for both the 5.2 and 6.4 run. I am looking for some pointers on what might be the cause for the significant difference in latency being reported between the two test runs on the versions noted. ACT-5.2-40x-results.txt ACT-6.4-40x-results.txt