> Magnus Hagander wrote:
> > I don't think that's correct either. Scatter/Gather I/O is used to
> > Server can issue reads for several blocks from disks into it's own
> > buffer cache with a single syscall even if these buffers are not
> > sequential. It did make significant performance improvements when
> > added it, though.
> > (For those not knowing - it's ReadFile/WriteFile where you pass an
> > of "this many bytes to this address" as parameters)
> Isn't that like the BSD writev()/readv() that Linux supports also? Is
> that something we should be using on Unix if it is supported by the
readv and writev are in the single unix spec...and yes they are
basically just like the win32 versions except that that are synchronous
(and therefore better, IMO).
On some systems they might just be implemented as a loop inside the
library, or even as a macro.
On operating systems that optimize vectored read operations, it's pretty
reasonable to assume good or even great performance gains, in addition
to (or instead of) recent changes to xlog.c to group writes together for
a file...it just takes things one stop further.
Is there a reason why readv/writev have not been considered in the past?
pgsql-performance by date
|Next:||From: Tom Lane||Date: 2005-02-21 16:27:29|
|Subject: Re: seq scan cache vs. index cache smackdown |
|Previous:||From: David Brown||Date: 2005-02-21 14:03:03|
|Subject: Re: bad performances using hashjoin|