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: Neil Conway <neilc@samurai.com>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Marc G. Fournier <scrappy@hub.org>
Cc: pgsql-committers@postgresql.org
Subject: Re: pgsql-server/ /configure /configure.in rc/incl ...
Date: Mon, 10 Mar 2003 21:30:33 -0800
Message-ID: <20030311053033.GH79234@perrin.int.nxad.com> (raw)
In-Reply-To: <2773.1047359174@sss.pgh.pa.us>
References: <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>
	<2773.1047359174@sss.pgh.pa.us>

> > 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
> 
> That change was not sold as a performance improvement; I doubt that
> it is one.  It was sold as not failing when libpq runs inside an
> application that has thousands of open files (i.e., more than
> select() can cope with).  "Faster" is debatable, "fails" is not...

Well, I've only heard through 2nd hand sources (dillion) the kind of
hellish conditions that Mark has on his boxen, but "faster and more
efficient in the kernel" is "faster and more efficient in the kernel"
no matter how 'ya slice it and I know that every last bit helps a
loaded system.

I'm not stating that most people, or even 90% of people, will notice.
Hopefully 100% of the universe runs their boxen under ideal conditions
(like most databases should, right?  ::wink wink, nudge nudge:: For
those that don't, however, and get to watch things run in the red with
a load average over 20, the use of kqueue or more efficient system
calls is likely very appreciated.  -sc

-- 
Sean Chittenden



view thread (22+ messages)

Message-ID: <20030311053033.GH79234@perrin.int.nxad.com>
Permalink:  ../20030311053033.GH79234@perrin.int.nxad.com/
Also on:    postgresql.org/message-id/20030311053033.GH79234@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, neilc@samurai.com, chriskl@familyhealth.com.au, scrappy@hub.org, pgsql-committers@postgresql.org
  Subject: Re: pgsql-server/ /configure /configure.in rc/incl ...
  In-Reply-To: <20030311053033.GH79234@perrin.int.nxad.com>
  References: <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> <2773.1047359174@sss.pgh.pa.us> <20030311053033.GH79234@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