| From: | Stephen Robert Norris <srn(at)commsecure(dot)com(dot)au> |
|---|---|
| To: | Justin Clift <justin(at)postgresql(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How to cripple a postgres server |
| Date: | 2002-05-28 21:10:30 |
| Message-ID: | 1022620230.23025.6.camel@chinstrap |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 2002-05-28 at 22:26, Justin Clift wrote:
> Hi Stephen,
>
> Are you able to give some detailed technical specs of the hardware
> you're running?
>
> I consider yours to be a higher-end PostgreSQL server, and I'd like to
> have a good practical understanding of what is required (hardware wise)
> to put together a 1k/second transaction PostgreSQL server.
>
> :-)
>
> Regards and best wishes,
>
> Justin Clift
It's nothing special - a dual Athlon (1600MHz or whatever), 1GB RAM, 4
UDMA IDE HDD.
The key trick is that we only have about 200MB or data to serve, and
thus never actually hit the disks...
On similar hardware, but with 3GB RAM and 160GB of data, we go back to a
more usual 30-50 random queries/second.
For background, the first system is part of a stock exchange information
system; the second is part of a bill presentation system.
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Burton | 2002-05-28 21:12:53 | Re: Database Rights |
| Previous Message | Stephen Robert Norris | 2002-05-28 21:08:40 | Re: How to cripple a postgres server |