

That’s a peak I think related to the converted image (some of my JPEG files in test directory are 40MB, 80MB, 170MB so loading them take naturally more space in memory) No surprise, generating cache with 4CPU instead of 24 is slowerĪlso, note that running on VM is naturally slower (not normal to be slow at his point on my computer, but normal)īut, it works without any problem (test made on 14000 files, 91GB average JPEG files are 7~9MB with some up to 170MB)Īt the maximum, Krita took I think 1.8GB RAM during cache generation. I think it’s a “normal” configuration to be able to run Windows 10 properly and available for most of users I’ve made a test on a Windows 10 running in VM with 4CPU/8GB RAM

I don’t have 80 or 60Gb of RAM to spare though I provided a possible solution, use it or not on my side I’m comfortable with results I have for my own case Other software were running properly (browsing or screen recording without any problem)Īlso, I currently let my plugin using all available thread, but it’s possible to tune this to tell him to only use 75% of 50% or less of thread (means: you let resources available for other task on computer)Īfter for a plugin like photobash, you do as you prefer, it’s not mine.Krita UI was still responsive (but Ok, not possible “to draw”).On my side, event with all CPU working to resize image and save results in cache: It will depend of your computer (mine is 24CPU / 60GB RAM but on my laptop 4CPU/16GB it’s slower :)) and how you’ve implemented things also Python is not the best language for this (a compiled language will provide better results in memory usage and speed) So giving support to folders of 60k seems impossible unless you filter search that and cache it after and still it would lag Once cache is generated, it took around ~1.2s to load 10000files thumbnails in a treeview Also load thumbnails asynchronously in treeview to keep ui responsiveīut the thing for performance is not only the use of multithreading, you have to generate a cache and use it.Use of threads allow to keep ui responsive while computer is doing intensive computation.Generating thumbnails (512, 256, 128 and 64px size thumbnail for each file) is a little bit longer (between ~50s and ~300s according to computer activity to generate 40000 thumbnails from 80GiB images – tested from a SSD, running with 24thread).

