Matthias Andree <[EMAIL PROTECTED]> wrote:
> 2. scheduling writes is a complex matter in itself, and there is not a
> single answer. The later you start writing, the more data you have
> available if the input rate is low for a while to write a large blob of
> data (reducing seeks), the more opportunity you have to rearrange writes
> and the lower the total amount of data to write, because updates of
> yet-unwritten data do not turn into writes (I/O) but are made in-core.
If you have the buffer cache at the right place and if you are able to
cluster to already pending requests (like on Solaris), things work different.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
