02-01-2024, 09:30 PM
Solved! The problem was specific to Hashtopolis, in the sense that the benchmark caused the chunks to be too small and therefore not enough work was attributed to the devices. Sometimes the benchmark returned correct results which caused the speed to increase. If the chunks are manually specified at the large enough size then the speed is even greater and almost reaches the theoretical benchmarks regardless of the large number of hashes located at the same time.