I think it's because squid scans 16 directories containing 256
directories each, in an order that's not good for the disk.
I'm not sure, but that seems like the obvious thing.
The obvious fix would be to scan the disk in a good order.
> > Netscape still hits the disk very hard when it starts, and takes what
> > seems like just as long. Netscape is pretty quick to start the second
> > time though (about 3 seconds), so it's definitely a paging thing. Is
> > there anything which could be done with paging
> > read-ahead/read-behind/read-cleverer to make Netscape not thrash the
> > disk when it starts?
>
> No, not really. When Netscape starts it is not in cache yet :)
I'm thinking that Netscape is only a "few" megabytes long, and it would
only take a second or so to read the executable and libraries in their
entirety. So we can blame read prediction for not knowing to do this
;-)
-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/