| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Christine Penner <christine(at)ingenioussoftware(dot)com> |
| Cc: | Postgres-General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Server Requirements |
| Date: | 2009-12-18 02:16:15 |
| Message-ID: | dcc563d10912171816r7e3a65a3kaf04a3e48c5fb6b1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Dec 16, 2009 at 4:21 PM, Christine Penner
<christine(at)ingenioussoftware(dot)com> wrote:
> Hi,
>
> If we have clients that are going to buy new computers or upgrade current
> ones, what we can recommend to them for optimal system performance to run
> Postgres. These can be servers or desktop PCs. We can have from 1-10 users
> in at a time. At this point all of our database's are small but that can
> change of course.
Like Craig said, your description is pretty vague, so it's hard to say
what you need most to make your pgsql server run fast.
Generally, the order of things to do to make it fast are: Add memory,
add hard drives, add battery backed caching RAID controllers, add more
CPU horsepower.
But it depends largely on your usage patterns. So, what are you doing
with your db?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gauthier, Dave | 2009-12-18 02:35:35 | Re: Justifying a PG over MySQL approach to a project |
| Previous Message | Scott Marlowe | 2009-12-18 02:06:35 | Re: Justifying a PG over MySQL approach to a project |