Re: FreeBSD random I/O performance issues

[Julian Elischer]

This is one of the things that made us do so badly
in the benchmarks against NT/Linux last year.
OBVIOUSLY one should be able to re-read this infoirmation
without affecting a pending write.

Mike Smith wrote:
> 
> >     effects of the I/O being in-progress.  If a user program doesn't access
> >     any of the information it recently wrote the whole mechanism winds up
> >     operating asynchronously in the background.  If a user program does,
> >     then the write behind mechanism breaks down and you get a stall.
> 
> What makes no sense is that it should be perfectly ok to _read_ this
> information back.
> 


-- 
      __--_|\  Julian Elischer
     /       \ [EMAIL PROTECTED]
    (   OZ    ) World tour 2000
---> X_.---._/  presently in:  Perth
            v


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message