Update: Removed because tests showed me that this idea below is only for really specifc and rare cases and it is not worth to create such feature. Maybe i will do some further tests in the future with other hardware. But as i said :) thank you for the software i love it.
Hey,
first thank you for your wonderful work. I did some Benchmarks with different algorithm and settings. It turns out that the wait IO and specificly the speed of the HDD / SDD has the most impact on the speed of hashing files.
I would like to suggest a option to load specific parts like Up to 16GB or more inside a virtual memory drive before processing with hashing, remove them and load the next blocks inside.
But i guess this solution will only result in a benefit if you got a lot of CPU Power for large ammount of files and for specific algorithm like Sha2 and Tiger
Update: Removed because tests showed me that this idea below is only for really specifc and rare cases and it is not worth to create such feature. Maybe i will do some further tests in the future with other hardware. But as i said :) thank you for the software i love it.
Hey,
first thank you for your wonderful work. I did some Benchmarks with different algorithm and settings. It turns out that the wait IO and specificly the speed of the HDD / SDD has the most impact on the speed of hashing files.
I would like to suggest a option to load specific parts like Up to 16GB or more inside a virtual memory drive before processing with hashing, remove them and load the next blocks inside.
But i guess this solution will only result in a benefit if you got a lot of CPU Power for large ammount of files and for specific algorithm like Sha2 and Tiger