On Wed, May 11, 2011 at 9:20 PM, Aren Cambre <a...@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. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
