Re: Postgres refusing to use >1 core - Mailing list pgsql-performance

From Scott Marlowe
Subject Re: Postgres refusing to use >1 core
Date
Msg-id BANLkTimz1ZLu=+_H_RfoXROwXQLvTJE80Q@mail.gmail.com
Whole thread Raw
In response to Re: Postgres refusing to use >1 core  (Aren Cambre <aren@arencambre.com>)
List pgsql-performance
On Wed, May 11, 2011 at 9:20 PM, Aren Cambre <aren@arencambre.com> wrote:
>> Using unix sockets, you can expect about 10-20.000 queries/s on small
>> simple selects per core, which is quite a feat. TCP adds overhead, so it's
>> slower. Over a network, add ping time.
>
> I'm talking to a Postgres on localhost, so in theory, I ought to be getting
> really good throughput, but again, the problem may be with the way C#'s
> PLINQ "multithreading in a can" is managing things.

local tcp is gonna be slower not faster than unix sockets, not faster.
 But the big issue is that you need to exlpore doing the work in a
large set not iteratively.  Operations on sets are often much faster
in aggregate.

pgsql-performance by date:

Previous
From: Robert Haas
Date:
Subject: Re: DBT-5 & Postgres 9.0.3
Next
From: Robert Haas
Date:
Subject: Re: Checkpoint execution overrun impact?