Messages in this thread | | | Date | Thu, 25 Sep 2003 07:18:01 +0200 | From | Gábor Lénárt <> | Subject | 2.6.0-testX: very slow directory reading? |
| |
Hello,
I've several quite large (~10000 mails) Maildirs, and using mutt as MUA. Opening such a maildir took some seconds with 2.4.x kernels (while seeing "Reading ..." message at the bottom with continously increasing number). However with 2.6.0-test3 and test5 the symptom is: reading the Maildir ("Reading ..." message) takes about the same emount of time as in 2.4. BUT: after reaching the last message, mutt waits even several MINUTES to show mail index page! While this, according to top, mutt is in 'D' state, and IO wait of the system is 100% (and if I try to do anything on other terminal, it takes a looooooooooooooooooong time). Is it a mutt or kernel related problem? Since I don't know internals of mutt, I can't know what mutt tries to do within that time ... Sorry for my mail, if it is not kernel related problem. I think it is some kernel related problem, since other applications also take quite long time (compared to 2.4.x) to read large directories. I don't understand this, because the key feature for me to use 2.6 (with htree included by default in the kernel, so no patch is needed) is the htree stuff to speed of handling of large directories ...
It's on ext3 fs with htree feature enabled, there was fsck with -f -D switches before.
Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: 21e9d65a-9e8c-49ef-a839-2a809df11e3a Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal dir_index filetype needs_recovery sparse_super Default mount options: (none) Filesystem state: clean Errors behavior: Remount read-only Filesystem OS type: Linux [...]
Kernel is 2.6.0-test5, but test3 was the same.
-- - Gábor (larta'H) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |