From: Christopher Weimann <cweimann@k12hq.com>
To: Mark Stosberg <mark@summersault.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Most effective tuning choices for busy website?
Date: Tue, 14 Jun 2005 19:59:37 -0400
Message-ID: <20050614235937.GA97567@tektite.k12usa.internal> (raw)
In-Reply-To: <slrnd9s2n5.ca0.mark@simba.summersault.com>
References: <slrnd9s2n5.ca0.mark@simba.summersault.com>
On 06/01/2005-07:19PM, Mark Stosberg wrote:
>
> - I saw the hardware tip to "Separate the Transaction Log from the
> Database". We have about 60% SELECT statements and 14% UPDATE
> statements. Focusing more on SELECT performance seems more important
> for us.
>
I would think that would help SELECT If the spindle isn't busy writing
Transaction log it can be reading for your SELECTs.
You did say you were CPU bound though.
--
------------------------------------------------------------
Christopher Weimann
http://www.k12usa.com
K12USA.com Cool Tools for Schools!
------------------------------------------------------------
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: cweimann@k12hq.com, mark@summersault.com
Subject: Re: Most effective tuning choices for busy website?
In-Reply-To: <20050614235937.GA97567@tektite.k12usa.internal>
* 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