| From: | Christopher Weimann <cweimann(at)k12hq(dot)com> |
|---|---|
| To: | Mark Stosberg <mark(at)summersault(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Most effective tuning choices for busy website? |
| Date: | 2005-06-14 23:59:37 |
| Message-ID: | 20050614235937.GA97567@tektite.k12usa.internal |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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!
------------------------------------------------------------
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2005-06-15 01:21:06 | Re: regular expression search |
| Previous Message | Mark Stosberg | 2005-06-14 22:34:52 | Re: Most effective tuning choices for busy website? |