From: Rod Taylor <pg@rbt.ca>
To: Jason Coene <jcoene@gotfrag.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Hardware upgrade for a high-traffic database
Date: Tue, 10 Aug 2004 19:06:52 -0400
Message-ID: <1092179211.11635.30.camel@jester> (raw)
In-Reply-To: <200408101917.i7AJHR0E064106@mail.gotfrag.com>
References: <200408101917.i7AJHR0E064106@mail.gotfrag.com>
> Our database is about 20GB on disk, we have some quite large tables - 2M
> rows with TEXT fields in a sample table, accessed constantly. We average
> about 4,000 - 5,000 queries per second - all from web traffic. As you can
99% is reads? and probably the same data over and over again? You might
want to think about a small code change to cache sections of page output
in memory for the most commonly generated pages (there are usually 3 or
4 that account for 25% to 50% of web traffic -- starting pages).
The fact you're getting 5k queries/second off IDE drives tells me most
of the active data is in memory -- so your actual working data set is
probably quite small (less than 10% of the 20GB).
If the above is all true (mostly reads, smallish dataset, etc.) and the
database is not growing very quickly, you might want to look into RAM
and RAM bandwidth over disk. An Opteron with 8GB ram using the same old
IDE drives. Get a mobo with a SCSI raid controller in it, so the disk
component can be upgraded in the future (when necessary).
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: pg@rbt.ca, jcoene@gotfrag.com
Subject: Re: Hardware upgrade for a high-traffic database
In-Reply-To: <1092179211.11635.30.camel@jester>
* 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