From: Sean Chittenden <sean@chittenden.org>
To: Neil Conway <neilc@samurai.com>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Marc G. Fournier <scrappy@hub.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-committers@postgresql.org
Subject: Re: pgsql-server/ /configure /configure.in rc/incl ...
Date: Mon, 10 Mar 2003 20:56:10 -0800
Message-ID: <20030311045610.GF79234@perrin.int.nxad.com> (raw)
In-Reply-To: <1047357755.357.1.camel@tokyo>
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>
<20030311041133.GC79234@perrin.int.nxad.com>
<018201c2e785$2c12c750$6500a8c0@fhp.internal>
<1047357755.357.1.camel@tokyo>
> > It would be nice to have this support there, however Tom was
> > correct in saying it really only applies to network apps that are
> > handling thousands of connections, all really, really fast.
> > Postgres doesn't. I say you'd have to do the work, then do the
> > benchmarking to see if it makes a difference.
>
> ... and if it doesn't make a significant difference, I'd oppose
> including it in the mainline source. Performance optimization is one
> thing; performance "optimization" that doesn't actually improve
> performance is another :-)
::sigh:: Well, I'm not about to argue one way or another on this
beyond saying: kqueue is better than select/poll, but there are much
bigger, much lower, and much easier pieces of fruit to pick off the
optimization tree given the cost/benefit for the amount of network IO
PostgreSQL does. That said, what was the performance gain of moving
from select() to poll()? It wasn't the biggest optimization in
PostgreSQL history, nor the smallest, but it was a step forward. -sc
--
Sean Chittenden
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, neilc@samurai.com, chriskl@familyhealth.com.au, scrappy@hub.org, tgl@sss.pgh.pa.us, pgsql-committers@postgresql.org
Subject: Re: pgsql-server/ /configure /configure.in rc/incl ...
In-Reply-To: <20030311045610.GF79234@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> <20030310224706.T35660@hub.org> <20030311041133.GC79234@perrin.int.nxad.com> <018201c2e785$2c12c750$6500a8c0@fhp.internal> <1047357755.357.1.camel@tokyo> <20030311045610.GF79234@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