Re: [Nautilus-list] Change committed that may affect the slowness

[Seth Nickell <snickell stanford edu>]

> > The only thing that occurs to me is that Nautilus could be waiting to
> > display until the directory counts are finished (?). I have yet to see
> > directory counts bubble in after display like I used to, but that could
> > be coincidental (e.g. something is freezing and the extra time means the
> > directory counts always finish).
> 
> hmm... another interesting thing is that the CPU usage by Nautilus is
> almost non-existant during the long waiting period. It sits around 6%,
> which might support the notion that its waiting for disk access.

Another interesting piece of data....

/dev loads almost instantly with no weird freezes (about 600 items in
/dev).

-Seth