I’ve set NetDrive cache to 500GB, but after running a lot of operations (a script is pulling files and processing them, then copying them to another folder), i see that it’s removing files that were pulled almost instantly and the cache folder is almost empty. I’ve noticed this by refreshing the cache folder (a jpg file that was recently pulled shows up, but after refreshing again it’s gone again.)
This creates unneccessary overhead by constantly doing pull/list requests from amazon, thus increasing my bill with amazon cloud service.
A user can set the cache expiration time manually by editng ndfs.ini.
The file path is “c:\Program Files (x86)\Bdrive\NetDrive3\x64\ndfs.ini” on 64bits OS.
Or “c:\Program Files (x86)\Bdrive\NetDrive3\ndfs.ini” on 32bits OS.
The sample file is attached. You need to rename it to ndfs.ini.
would be great if netdrive handled caches differently.
i.e.
Cache all files without time limit and as the allocated drive space is reached, remove as many files as neccessary (based on least access time to cache new files)