pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marc G. Fournier <scrappy@hub.org>
To: Sean Chittenden <sean@chittenden.org>
Cc: 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: Mon, 10 Mar 2003 22:50:59 -0400 (AST)
Message-ID: <20030310224706.T35660@hub.org> (raw)
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>

yOn Thu, 6 Mar 2003, Sean Chittenden wrote:

> > >>> 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.

I would personally be interested in seeing patches ... what would be
involved?




view thread (22+ messages)  latest in thread

Message-ID: <20030310224706.T35660@hub.org>
Permalink:  ../20030310224706.T35660@hub.org/
Also on:    postgresql.org/message-id/20030310224706.T35660@hub.org

 · 

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: scrappy@hub.org, 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: <20030310224706.T35660@hub.org>
  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> <20030310224706.T35660@hub.org>

* 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