Added to TODO:
* Experiment with multi-threaded backend better resource utilization
This would allow a single query to make use of multiple CPU's or
multiple I/O channels simultaneously.
On Thu, Mar 23, 2006 at 09:22:34PM -0500, Christopher Browne wrote:
Martha Stewart called it a Good Thing when [EMAIL PROTECTED] (Scott Marlowe)
wrote:
On Thu, 2006-03-23 at 10:43, Joshua D. Drake wrote:
Has someone been working on the problem of splitting a query into pieces
and
Christopher,
On 3/23/06 6:22 PM, Christopher Browne [EMAIL PROTECTED] wrote:
Question: Does the Bizgress/MPP use threading for this concurrency?
Or forking?
If it does so via forking, that's more portable, and less dependent on
specific complexities of threading implementations (which
[EMAIL PROTECTED] (Jim C. Nasby) writes:
On Thu, Mar 23, 2006 at 09:22:34PM -0500, Christopher Browne wrote:
Martha Stewart called it a Good Thing when [EMAIL PROTECTED] (Scott Marlowe)
wrote:
On Thu, 2006-03-23 at 10:43, Joshua D. Drake wrote:
Has someone been working on the problem of
[EMAIL PROTECTED] (Luke Lonergan) writes:
Christopher,
On 3/23/06 6:22 PM, Christopher Browne [EMAIL PROTECTED] wrote:
Question: Does the Bizgress/MPP use threading for this concurrency?
Or forking?
If it does so via forking, that's more portable, and less dependent on
specific
On Fri, Mar 24, 2006 at 01:21:23PM -0500, Chris Browne wrote:
A naive read on this is that you might start with one backend process,
which then spawns 16 more. Each of those backends is scanning through
one of those 16 files; they then throw relevant tuples into shared
memory to be
On Fri, Mar 24, 2006 at 01:21:23PM -0500, Chris Browne wrote:
Correct me if I'm wrong, but there's no way to (reasonably) accomplish
that without having some dedicated extra processes laying around that
you can use to execute the queries, no? In other words, the cost of a
fork() during
[EMAIL PROTECTED] (Michael Stone) writes:
On Fri, Mar 24, 2006 at 01:21:23PM -0500, Chris Browne wrote:
A naive read on this is that you might start with one backend process,
which then spawns 16 more. Each of those backends is scanning through
one of those 16 files; they then throw relevant
[EMAIL PROTECTED] (Jojo Paderes) wrote:
I'd like to know if the latest PostgreSQL release can scale up by
utilizing multiple cpu or dual core cpu to boost up the sql
executions.
I already do a research on the PostgreSQL mailing archives and only
found old threads dating back 2000. A lot of
On Thu, 23 Mar 2006 14:19:24 +0800
Jojo Paderes [EMAIL PROTECTED] wrote:
I'd like to know if the latest PostgreSQL release can scale up by
utilizing multiple cpu or dual core cpu to boost up the sql
executions.
I already do a research on the PostgreSQL mailing archives and only
found old
On Thu, 2006-03-23 at 00:19, Jojo Paderes wrote:
I'd like to know if the latest PostgreSQL release can scale up by
utilizing multiple cpu or dual core cpu to boost up the sql
executions.
I already do a research on the PostgreSQL mailing archives and only
found old threads dating back 2000.
Has someone been working on the problem of splitting a query into pieces
and running it on multiple CPUs / multiple machines? Yes. Bizgress has
done that.
I believe that is limited to Bizgress MPP yes?
---(end of broadcast)---
TIP 9: In
On Thu, 2006-03-23 at 10:43, Joshua D. Drake wrote:
Has someone been working on the problem of splitting a query into pieces
and running it on multiple CPUs / multiple machines? Yes. Bizgress has
done that.
I believe that is limited to Bizgress MPP yes?
Yep. I hope that someday it
Martha Stewart called it a Good Thing when [EMAIL PROTECTED] (Scott Marlowe)
wrote:
On Thu, 2006-03-23 at 10:43, Joshua D. Drake wrote:
Has someone been working on the problem of splitting a query into pieces
and running it on multiple CPUs / multiple machines? Yes. Bizgress has
done
I'd like to know if the latest PostgreSQL release can scale up by
utilizing multiple cpu or dual core cpu to boost up the sql
executions.
I already do a research on the PostgreSQL mailing archives and only
found old threads dating back 2000. A lot of things have improved with
PostgreSQL and
15 matches
Mail list logo
