Re: seq scan cache vs. index cache smackdown
От | Merlin Moncure |
---|---|
Тема | Re: seq scan cache vs. index cache smackdown |
Дата | |
Msg-id | 6EE64EF3AB31D5448D0007DD34EEB3412A762F@Herge.rcsinc.local обсуждение исходный текст |
Ответ на | seq scan cache vs. index cache smackdown (Mark Aufflick <mark@pumptheory.com>) |
Ответы |
Re: seq scan cache vs. index cache smackdown
Re: seq scan cache vs. index cache smackdown |
Список | pgsql-performance |
> Magnus Hagander wrote: > > I don't think that's correct either. Scatter/Gather I/O is used to SQL > > 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 they > > added it, though. > > > > (For those not knowing - it's ReadFile/WriteFile where you pass an array > > 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 OS? 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. http://www.opengroup.org/onlinepubs/007908799/xsh/sysuio.h.html 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? Merlin
В списке pgsql-performance по дате отправления: