Skip site navigation (1) Skip section navigation (2)

Re: Scaling up PostgreSQL in Multiple CPU / Dual Core

From: Michael Stone <mstone+postgres(at)mathom(dot)us>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Scaling up PostgreSQL in Multiple CPU / Dual Core
Date: 2006-03-24 19:21:24
Message-ID: 20060324192122.GJ15140@mathom.us (view raw or flat)
Thread:
Lists: pgsql-performance
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 aggregated/joined by the central one.

Of course, table scanning is going to be IO limited in most cases, and 
having every query spawn 16 independent IO threads is likely to slow 
things down in more cases than it speeds them up. It could work if you 
have a bunch of storage devices, but at that point it's probably easier 
and more direct to implement a clustered approach.

Mike Stone

In response to

Responses

pgsql-performance by date

Next:From: Tom LaneDate: 2006-03-24 19:23:49
Subject: Re: Performance problems with multiple layers of functions
Previous:From: Svenne KrapDate: 2006-03-24 19:16:29
Subject: Re: Performance problems with multiple layers of functions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group