Leaderboard

At least when testing on my own machines there is caching going on - but my opinion is that's being done by Windows since caching file system queries is part of a modern operating system's job description and having DrivePool do it too seems like it would be redundant (although I know dedicated caching programs e.g. PrimoCache do exist). Certainly there's nothing in DrivePool's settings that mentions caching. Whether a disk gets woken by a particular directory query is going to depend on whether that query can be answered by what's in the cache from previous queries.

To quote my response to Christopher: " If I'm understanding the rest of your explanation correctly, you're saying that anytime the application needs to retrieve a file from any disk in the pool all of the disks will wake up from sleep so that DrivePool can determine upon which disk a file is residing in order to deliver it back to the application. Is that correct?" Your response still doesn't answer it clearly. Is there caching or isn't there? Will the drives wake up any time there is an application that needs to retrieve a file from any disk, or does DrivePool mitigate that somehow? Should I expect to see disk activity on all disks any time a file on a single disk is retrieved or are there times when DrivePool can deliver file location information without waking every disk?

To quote Christopher from that thread, "StableBit DrivePool pulls the directory list for the pool directly from the disks, and merges them in memory, basically. So if you have something that is scanning the folders, you may see activity." There may be some directory/file list caching going on in RAM, whether at the Windows OS and/or DrivePool level, but DrivePool itself does not keep any form of permanent (disk-based, reboot-surviving) record of directory contents.

@Katz777I just went through this recently after setting it up several months ago. I use Scanner, DrivePool, and CloudDrive. I had to update my Scanner settings not to query SMART more often than once per hour, and not to wake drives to query. I also had to disable BitLocker detection in the JSON config file. I didn't need to do anything with CloudDrive. Once I made those changes and a couple of Windows config changes everything worked fine. Last time I updated DrivePool the BitLocker detection flag was reset to default and the drives wouldn't sleep anymore. I did need to enable options 13 and 15 as described in this post in order to set the power options that worked for me. https://www.thewindowsclub.com/configure-hidden-power-options-in-windows-10

Is that true? I asked for clarity on this exactly several days ago but never got a response.