I’ve never been able to use the app without setting it to use more memory, e.g. with 20K files on a network share I have to set the memory to 2GB.
The user experience with too little memory is not great, either files fail to load (defaul settings), increase and start again (1GB), then during tagging it would complain again about too little memory, now what (set to 2GB and restart).
Why not set the app to use all memory, like a native app would have, the memory would be paged out anyway?
Because there is a problem with macs that if you allocate more memory then is physically available Jaikoz runs too slow. It was never really the intention that you load all 20,000 files in one go but because everybody seems to be doing this I will be working on some kind of cache.
Paul,
This is the only “Major” problem I have had with your program. Even with setting memory to 4GB I can not load more then 10k files and have it complete auto correct. Can we move this from “wish” to reality 
Thanks,
Tim
If you still cant load more than 10k either you havent set the memory correctly or you have a problem with a particular file consuming masses of memory.
I believe a couple of people have encountered the second problem, but I have no proof. If you are continually failing to load files after at about the same folder despite changes to memory, could you try just loading that folder to see if it still fails and then you can narrow the fault down and send me the problem file.
Jaikoz 2.5.0 will show in the console the maximum memory its thinks you have allocated, it also contains many memory usage improvements