From: | Doug McNaught <doug(at)wireboard(dot)com> |
---|---|
To: | nconway(at)klamath(dot)dyndns(dot)org (Neil Conway) |
Cc: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Threaded PosgreSQL server |
Date: | 2002-02-06 20:24:04 |
Message-ID: | m3d6zi1hqz.fsf@varsoon.denali.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
nconway(at)klamath(dot)dyndns(dot)org (Neil Conway) writes:
> However, I think using threads is only a good idea if it gets us a
> substantial performance increase. From what I've seen, that isn't the
> case; and even if the time to create a connection is a bottleneck, there
> are other, more conservative ways of improving it (e.g. pre-forking,
> persistent backends, and IIRC some work Tom Lane was doing to reduce
> backend startup time).
The one place where it could be a clear win would be in splitting
single very large queries over multiple CPUs. This would probably
require an even larger redesign of the whole system than moving to a
query-per-thread rather than per-process model. I think "real"
multi-master replication and clustering is a better goal in the short
term...
-Doug
--
Let us cross over the river, and rest under the shade of the trees.
--T. J. Jackson, 1863
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 2002-02-06 20:47:45 | JOIN between three *simple* tables ... |
Previous Message | mlw | 2002-02-06 20:15:55 | Re: [GENERAL] PostgreSQL v7.2 Final Release |