pg.ddx.io pgsql-performance@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Ron <rjpeace@earthlink.net>
To: Thomas Harold <tgh@tgharold.com>
To: pgsql-performance@postgresql.org
Subject: Re: two disks - best way to use them?
Date: Tue, 06 Dec 2005 03:12:31 -0500
Message-ID: <6.2.5.6.0.20051206030948.01dd4bb0@earthlink.net> (raw)
In-Reply-To: <4395273B.90902@tgharold.com>
References: <00fb01c5f772$59471410$0200a8c0@dell8200>
<6.2.5.6.0.20051202145746.01dc7b68@earthlink.net>
<43946148.9010607@tgharold.com>
<Pine.LNX.4.62.0512050808440.2807@qnivq.ynat.uz>
<43946EA1.8090908@tgharold.com>
<Pine.LNX.4.62.0512051950560.2807@qnivq.ynat.uz>
<4395273B.90902@tgharold.com>
At 12:52 AM 12/6/2005, Thomas Harold wrote:
>David Lang wrote:
>
>>in that case you logicly have two disks, so see the post from Ron
>>earlier in this thread.
>
>And it's a very nice performance gain. Percent spent waiting
>according to "top" is down around 10-20% instead of 80-90%. While
>I'm not prepared to benchmark, database performance is way up. The
>client machines that are writing the data are running closer to 100%
>CPU (before they were well below 50% CPU utilization).
For accuracy's sake, which exact config did you finally use?
How did you choose the config you finally used? Did you test the
three options or just pick one?
Ron
view thread (11+ messages) latest in thread
Message-ID: <6.2.5.6.0.20051206030948.01dd4bb0@earthlink.net> Permalink: ../6.2.5.6.0.20051206030948.01dd4bb0@earthlink.net/ Also on: postgresql.org/message-id/6.2.5.6.0.20051206030948.01dd4bb0@earthlink.net ·
reply
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: rjpeace@earthlink.net, tgh@tgharold.com Subject: Re: two disks - best way to use them? In-Reply-To: <6.2.5.6.0.20051206030948.01dd4bb0@earthlink.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