From: | Carlos Moreno <moreno_pg(at)mochima(dot)com> |
---|---|
To: | Daniel Griscom <griscom(at)suitable(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Throttling PostgreSQL's CPU usage |
Date: | 2007-05-09 14:29:56 |
Message-ID: | 4641DAE4.4020805@mochima.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Daniel Griscom wrote:
> Thanks again for all the feedback. Running on a dual processor/core
> machine is clearly a first step, and I'll look into the other
> suggestions as well.
As per one of the last suggestions, do consider as well putting a dual
hard disk
(as in, independent hard disks, to allow for simultaneous access to
both). That
way, you can send the WAL (px_log directory) to a separate physical drive
and improve performance (reduce the potential for bottlenecks) if there
is a
considerable amount of writes. With Windows, you can mount specific
directories to given HD partitions --- that would do the trick.
Also, of course, do make sure that you give it a generous amount of RAM, so
that an as-large-as-possible fraction of the read operations are done
directly
off the machine's memory.
BTW, have you considered using a *separate* machine for PostgreSQL?
(that way this machine could be running on Linux or some Unix flavor,
and the Windows machine is dedicated to the ActiveX rendering stuff).
I mean, if you are going to get a new machine because you need to replace
it, you might as well get a new machine not as powerful, since now you
will have the dual-CPU given by the fact that there are two machines.
Good luck!
Carlos
--
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2007-05-09 14:29:58 | Re: Poor performance with queries using clause: sth IN (...) |
Previous Message | Alvaro Herrera | 2007-05-09 14:29:14 | Re: Apparently useless bitmap scans |