I have 400 images in a directory. I look at the directory with nautilus.
The first time I open the directory it is very slow. I have a modern laptop with 4 cores and plenty of RAM.
My use case:
- open directory containing a lot of images
- press Ctrl++ to make the images larger
- I want to sort the images to some directories, or delete some images.
Result:
- Nautilus is unusably slow. I walked away from the laptop to do different stuff, some time later it was usable.
- Nautilus has 104% CPU in top.
- Low "wait" value in top: Disk is not the bottleneck
Guess:
- Nautilus creates the thumbnails of all images, without nice-level.
- But all thumbnails are not needed at once. I just looked at the first 10 images.
- Nautilus should prefer user input to background thumbnail creation, since user response is more important.
- Multicores hang around idle.
My conclusion:
- if Nautilus would use all cores and with a nice value for background stuff, the user would have better responsiveness and the background job would be quicker.
Question: Is there anything I can do to solve this?
Maybe a configuration which can I set, or create a bug report for the developers?
