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

Re: dbt-2 tuning results with postgresql-8.3.5

From: "Mark Wong" <markwkm(at)gmail(dot)com>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: "Gabrielle Roth" <gorthx(at)gmail(dot)com>, "Selena Deckelmann" <selenamarie(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: dbt-2 tuning results with postgresql-8.3.5
Date: 2009-01-14 03:49:25
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Tue, Jan 13, 2009 at 7:40 AM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
>>>> "Mark Wong" <markwkm(at)gmail(dot)com> wrote:
>> It appears to peak around 220 database connections:
> Interesting.  What did you use for connection pooling?

It's a fairly dumb but custom built C program for the test kit:;a=summary

I think the bulk of the logic is in src/client.c, src/db_threadpool.c,
and src/transaction_queue.c.

> My tests have never stayed that flat as the connections in use
> climbed.  I'm curious why we're seeing such different results.

I'm sure the difference in workloads makes a difference.  Like you
implied earlier, I think we have to figure out what works best in for
our own workloads.


In response to

pgsql-performance by date

Next:From: Maksim SosnovskiyDate: 2009-01-14 05:53:52
Subject: index
Previous:From: Jeff FrostDate: 2009-01-13 23:44:00
Subject: Re: strange index behaviour with different statistics target

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