Louis Horvath

Thank you for the response! You are right, I was being a bit naive about the work being put into reading files. THAT BEING SAID ... does the verification need to be done at the moment files are loaded into FO? What if that verification was done at the moment the file is about to be optimized? It would have the benefit of boosting the loading of files initially while not loosing any of the verifications done by FO. I figure, you're gonna work on the file anyways so might as well do most of it in the...

I did a little script in AutoIT3 that shows how long it takes for an interpreted language to load 4533 files into an array. Full comments so you can figure out what each line does. TLDR : According to AutoIT It takes ~150 miliseconds. ; Create array from a specified folder. Compare with FileOptimizer Opt("MustDeclareVars", 1) ; All variables must be created before they are used. #include <Array.au3> #include <File.au3> #include <Timers.au3> Global $aDir ; Will hold an array to contain filenames Global...

Rebooted my machine, same folder takes ~42 seconds to load. When in cache it takes ~22 seconds to load. Note : dir command is nearly instantaneous. It's not a file system slowdown.

This is not a bug per se but when I load files into FileOptimizer it looks like a very laborious process I have a folder with ~4500 files and it takes about 15-20 seconds to display the listing of the files During that time FileOptimizer doesn't say anything and the interface is frozen. I'm not noticing any wild CPU usage. I'm assuming FileOptimizer is already using the system cache to accelerate the process I've done programming before and this is a simple 2D array: filename + size. This issue is...

This is not a bug per se but when I load files into FileOptimizer it looks like a very laborious process I have a folder with ~4500 files and it takes about 15-20 seconds to display the listing of the files During that time FileOptimizer doesn't say anything and the interface is frozen. I'm not noticing any wild CPU usage. I'm assuming FileOptimizer is already using the system cache to accelerate the process I've done programming before and this is a simple 2D array: filename + size. This issue is...

Got a beta version from @fhanau. Testing as we speak.

Got a beta versio from @fhanau. Testing as we speak.

All tests done, now it's up to @fhanau to find out where the issue is.