Nautilus is very slow when opening folders with many files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nautilus |
Fix Released
|
Unknown
|
|||
nautilus (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Opening folders with many files takes a long time with Nautilus, to the point it becomes unusable for folders with more than 5K files.
I've measured the time it takes for folders with different amount of files to open with Nautilus and Gnome Commander. It is ~6 times faster with GC on average. In folders with ~20K files, it takes 30s with nautilus versus 6! with GC.
With Nautilus
~3500 files tales 6 seconds
~7000 files takes 18 seconds
~15000 files takes 22 seconds
~20000 files takes 30 seconds
With Gnome Commander
~3500 files tales <1 second
~7000 files takes 1.5 seconds
~15000 files takes 3 seconds
~20000 files takes 6 seconds
These are mostly small dicom files (MRI images). I am using a 8 core 3.4Ghz and 16Gigs of RAM with Ubuntu 11.04 64-bits.
Also, of course, things like selecting all files and copying them around is absurdly slow and makes nautilus unusable... but that would be another bug report (?).
Changed in nautilus: | |
importance: | Unknown → Low |
status: | Unknown → Confirmed |
Changed in nautilus (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in nautilus: | |
importance: | Low → High |
tags: | added: amd64 i386 precise quantal ubuntu |
Changed in nautilus (Ubuntu): | |
status: | Triaged → Incomplete |
status: | Incomplete → Confirmed |
Changed in nautilus: | |
status: | Confirmed → Invalid |
Changed in nautilus: | |
importance: | High → Unknown |
status: | Invalid → Unknown |
Changed in nautilus: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Changed in nautilus: | |
status: | Confirmed → Invalid |
Changed in nautilus: | |
status: | Unknown → New |
tags: | removed: natty precise quantal raring |
Changed in nautilus: | |
status: | New → Fix Released |
Changed in nautilus (Ubuntu): | |
status: | Confirmed → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.