From: Andy Colson <andy@squeakycode.net>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: Walker, James Les <JAWalker@cantor.com>
Cc: Thomas Kellerer <spam_eater@gmx.net>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Tuning Postgres 9.1 on Windows
Date: Tue, 01 May 2012 08:42:14 -0500
Message-ID: <4F9FE836.5010301@squeakycode.net> (raw)
In-Reply-To: <CAHyXU0xVG0foc24qeLexc54qtoVNuX8bMX1UcSP3foe3oUnexQ@mail.gmail.com>
References: <21BFB59709EBB84DB412ED7F739FFD3B19E5E3@TBPINFN0203.cad.local>
<CAHyXU0wSzBma5=X+fudsCJDiOoWtvVcH06YU_AbgugeorWhNFw@mail.gmail.com>
<jnn219$oou$1@dough.gmane.org>
<CAHyXU0wZJVeHbGDTRerh41iN6PfJNhDxvDJRdxbmUVx_U58JDA@mail.gmail.com>
<21BFB59709EBB84DB412ED7F739FFD3B1AC2C2@TBPINFN0203.cad.local>
<CAHyXU0xVG0foc24qeLexc54qtoVNuX8bMX1UcSP3foe3oUnexQ@mail.gmail.com>
On 5/1/2012 8:06 AM, Merlin Moncure wrote:
> On Tue, May 1, 2012 at 7:51 AM, Walker, James Les<JAWalker@cantor.com> wrote:
>> Exactly, if turning off fsync gives me 100 commits/sec then I know where my bottleneck is and I can attack it. Keep in mind though that I already turned off synchronous commit -- *really* dangerous -- and it didn't have any effect.
>
> well synchronous commit is not as dangerous:
> fsync off + power failure = corrupt database
> synchronous commit off + power failure = some lost transactions
>
> still waiting on the ssd model #. worst case scenario is that you tps
> rate is in fact sync bound and you have a ssd without capacitor backed
> buffers (for example, the intel 320 has them); the probable workaround
> would be to set the drive cache from write through to write back but
> it would unsafe in that case. in other words, tps rates in the triple
> digits would be physically impossible.
>
> another less likely scenario is you are having network issues
> (assuming you are connecting to the database through tcp/ip). 20
> years in, microsoft is still figuring out how to properly configure a
> network socket.
>
> merlin
>
Even if its all local, windows doesnt have domain sockets (correct?), so
all that traffic still has to go thru some bit of network stack, yes?
-Andy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: andy@squeakycode.net, mmoncure@gmail.com, JAWalker@cantor.com, spam_eater@gmx.net
Subject: Re: Tuning Postgres 9.1 on Windows
In-Reply-To: <4F9FE836.5010301@squeakycode.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox