pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Sean Chittenden <sean@chittenden.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: pgsql-committers@postgresql.org
Subject: Re: pgsql-server/ /configure /configure.in rc/incl ...
Date: Thu, 6 Mar 2003 01:41:17 -0800
Message-ID: <20030306094117.GA79234@perrin.int.nxad.com> (raw)
In-Reply-To: <12228.1046922471@sss.pgh.pa.us>
References: <20030306031656.1876F4762E0@postgresql.org>
	<032f01c2e390$b1842b20$6500a8c0@fhp.internal>
	<11077.1046921667@sss.pgh.pa.us>
	<033f01c2e392$71476570$6500a8c0@fhp.internal>
	<12228.1046922471@sss.pgh.pa.us>

> >>> Has anyone ever thought about adding kqueue (for *BSD) support to
> >>> Postgres, instead of using select?
> >> 
> >> Why?  poll() is standard.  kqueue isn't, AFAIK.
> 
> > It's supposed be a whole heap faster - there is no polling involved...
> 
> Supposed by whom?  Faster than what?  And how would it not poll?
> 
> The way libpq uses this call, it's either probing for current status
> (timeout=0) or it's willing to block, possibly indefinitely, until the
> desired condition arises.  It does not sit there in a busy-wait loop.
> I can't see any reason to think that an OS-specific API would give
> any marked difference in performance.

Heh, kqueue is _the_ reason to use FreeBSD.

http://www.kegel.com/dkftpbench/Poller_bench.html#results

I've toyed with the idea of adding this because it is monstrously more
efficient than select()/poll() in basically every way, shape, and
form.

That said, in terms of performance perks, I'd think migrating the
backend to using mmap() would yield a bigger performance benefit (see
Stevens) to a larger group of people than adding FreeBSD's kqueue
interface (something I plan on doing at some point if no one beats me
to it).  mmap() + write() for FreeBSD is a zero-copy socket operation
and likely is on other platforms.  Reducing the number of pages that
have to be copied around would be a big win in terms of sending data
to clients as well as scanning through data.  Files are also only
mmap()'ed in the kernel once with BSD's VM system which could reduce
the RAM consumed by backends considerably.

mmap() would also be an interesting way of providing some kind of
atomicity for MVCC (re: WAL, use msync() to have the mapped region hit
the disk before the change). I was actually quite surprised when I
grep'ed through the code and found that mmap() wasn't in use
_anywhere_.  The TODO seems to be full of messages, but not much in
the way of authoritative statements.  Is this one of the areas of
PostgreSQL that just needs to get slowly migrated to use mmap() or are
there any gaping reasons why to not use the family of system calls?

-sc

-- 
Sean Chittenden

view thread (22+ messages)  latest in thread

Message-ID: <20030306094117.GA79234@perrin.int.nxad.com>
Permalink:  ../20030306094117.GA79234@perrin.int.nxad.com/
Also on:    postgresql.org/message-id/20030306094117.GA79234@perrin.int.nxad.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: sean@chittenden.org, tgl@sss.pgh.pa.us, chriskl@familyhealth.com.au, pgsql-committers@postgresql.org
  Subject: Re: pgsql-server/ /configure /configure.in rc/incl ...
  In-Reply-To: <20030306094117.GA79234@perrin.int.nxad.com>
  References: <20030306031656.1876F4762E0@postgresql.org> <032f01c2e390$b1842b20$6500a8c0@fhp.internal> <11077.1046921667@sss.pgh.pa.us> <033f01c2e392$71476570$6500a8c0@fhp.internal> <12228.1046922471@sss.pgh.pa.us> <20030306094117.GA79234@perrin.int.nxad.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox