Force one thread
Posted: Wed May 09, 2012 6:16 am
Hi Romex Team,
I have no idea the following is even part of what caching software should do; but I'll ask anyway because it can speed up diskaccess greatly in certain situations.
We all know many drives can't handle multiple threads (read/write actions very well)
That's especially true for external USB2 drives.
One thread gives a read of 30MB/s (just an example)
3 threads give a total speed of 10MB/s
My idea/request is this. FancyCache works xxx seconds on each thread on that USB drive. That way the drive works at top speed for xxx second.
xxx = user configureble. Personally I would set it at 20 seconds.
I only use external drives for backups so for me it's only the total time that counts. The fact that the non active threads have to wait is of no concern to me.
The only thing Í don't know is how Windows would react to the above suggestion. The third thread has to wait 2x20=40 seconds. Will Windows give an error because it assumes the drive is offline/removed/damaged?
What I'm asking is a little similar to NCQ used in (almost) all SATA drives. I've never seen that for USB drives.
I have no idea the following is even part of what caching software should do; but I'll ask anyway because it can speed up diskaccess greatly in certain situations.
We all know many drives can't handle multiple threads (read/write actions very well)
That's especially true for external USB2 drives.
One thread gives a read of 30MB/s (just an example)
3 threads give a total speed of 10MB/s
My idea/request is this. FancyCache works xxx seconds on each thread on that USB drive. That way the drive works at top speed for xxx second.
xxx = user configureble. Personally I would set it at 20 seconds.
I only use external drives for backups so for me it's only the total time that counts. The fact that the non active threads have to wait is of no concern to me.
The only thing Í don't know is how Windows would react to the above suggestion. The third thread has to wait 2x20=40 seconds. Will Windows give an error because it assumes the drive is offline/removed/damaged?
What I'm asking is a little similar to NCQ used in (almost) all SATA drives. I've never seen that for USB drives.