By way of introduction, an exemplary snapshot from current processes:
#+begin_example
/lib/x86_64-linux-gnu/libexec/kf5/kioslave5 /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/thumbnail.so thumbnail local:/run/user/1000/dolphiniybvSu.112.kioworker.socket
#+end_example
Especially in larger archives and on optical disks parallelization could be faster and therefore less annoying. I thought about CPU threads/2 at low priority (idle/best-effort). Do you think this makes sense too or are there reasons against it?
2 Likes
I have been affected by this too.
And this is relevant.
I made a directory with all the images [~500px width] required for the thumbnails and a .directory file in multiple subdirs of a directory on a removable HDD.
When I first open it after a restart, it tends to take a few seconds for the directory to load.
It would be good to have the directory contents load first and let the thumbnails take their own merry time.
Also, this implementation would be augmented by the automatic parallelisation/serialisation functionality in KIO.