From: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org> |
---|---|
To: | Sean Chittenden <sean(at)chittenden(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql-server/ /configure /configure.in rc/incl ... |
Date: | 2003-03-11 02:50:59 |
Message-ID: | 20030310224706.T35660@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-performance |
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?
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Chittenden | 2003-03-11 04:11:33 | Re: pgsql-server/ /configure /configure.in rc/incl ... |
Previous Message | Tom Lane | 2003-03-10 22:28:22 | pgsql-server/ ontrib/dbase/dbf2pg.c ontrib/ful ... |
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Brown | 2003-03-11 03:44:36 | Re: Index / Performance issues |
Previous Message | Tom Lane | 2003-03-10 20:07:54 | Re: Large difference between elapsed time and run time for queries |