Re: Roadmap for a Win32 port
Yeah: ST is designed for network apps, and its for network bound apps that
you
gain the most performance - but by using it to allow
a child process to hold multiple connections and accept/return data to
those connections simultaneously, I forsaw a potential performance
improvement...
*shrug* Most connections remain idle most of thier life... yes?
the SGI folks developed this library as part of a project to make apache
faster (http://aap.sourceforge.net/) - multiple child
processes as normal, but allowed multiple connections per child.
And although the performance improvements they got were greatest on irix,
performance was improved upto 70% on linux. Some of this was from QSC
(http://aap.sourceforge.net/mod_qsc.html) , however...
just some food for thought.
----- Original Message -----
From: "Neil Conway" <nconway@klamath.dyndns.org>
To: "Jon Franz" <coventry@one.net>
Cc: <pgsql-hackers@postgresql.org>
Sent: Wednesday, June 05, 2002 8:05 PM
Subject: Re: [HACKERS] Roadmap for a Win32 port
On Wed, 5 Jun 2002 18:50:46 -0400
"Jon Franz" <coventry@one.net> wrote:One note: SGI developers discovered they could get amazing performance
using
as hybrid threaded and forked-process model with apache - we might want
to
Show quoted text
look into this. They even have a library for network-communication
utilizing thier 'state threads' model.I think ST is designed for network I/O-bound apps -- last I checked,
disk I/O will still block an entire ST process. While you can get around
that by using another process to do disk I/O, it sounds like ST won't be
that useful.However, Chris KL. (I believe) raised the idea of using POSIX AIO for
PostgreSQL. Without having looked into it extensively, this technique
sounds promising. Perhaps someone who has looked into this further
(e.g. someone from Redhat) can comment?Cheers,
Neil
--
Neil Conway <neilconway@rogers.com>
PGP Key ID: DB3C29FC---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
Import Notes
Reference msg id not found: 200206052005.g55K52615577@candle.pha.pa.usReference msg id not found: 001201c20ce36e21bed0a1ed03c7@dev.ngcnReference msg id not found: 20020605200544.4a486fe4.nconway@klamath.dyndns.org