From: Mike Rylander <mrylander@gmail.com>
To: Chris Kratz <chris.kratz@vistashare.com>
Cc: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance Tuning
Date: Thu, 10 Feb 2005 01:27:16 +0000
Message-ID: <b918cf3d0502091727267dd57d@mail.gmail.com> (raw)
In-Reply-To: <200502091730.41997.chris.kratz@vistashare.com>
References: <6EE64EF3AB31D5448D0007DD34EEB3412A7615@Herge.rcsinc.local>
<200502091730.41997.chris.kratz@vistashare.com>
On Wed, 9 Feb 2005 17:30:41 -0500, Chris Kratz
<chris.kratz@vistashare.com> wrote:
> The solutions appear to primarily be:
> 1. Going to faster hardware of which probably Opterons would be about the only
> choice. And even that probably won't be a huge difference.
I'd beg to differ on that last part. The difference between a 3.6GHz
Xeon and a 2.8GHz Opteron is ~150% speed increase on the Opteron on my
CPU bound app. This is because the memory bandwidth on the Opteron is
ENORMOUS compared to on the Xeon. Add to that the fact that you
actually get to use more than about 2G of RAM directly and you've got
the perfect platform for a high speed database on a budget.
> 2. Moving to more materialized views and prepared statements where we can.
Definitely worth investigating. I wish I could, but I can't get my
customers to even consider slightly out of date stats.... :(
> 3. Continue to tweak the sql behind our app.
Short of an Opteron based system, this is by far your best bet.
--
Mike Rylander
mrylander@gmail.com
GPLS -- PINES Development
Database Developer
http://open-ils.org
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: mrylander@gmail.com, chris.kratz@vistashare.com, merlin.moncure@rcsonline.com
Subject: Re: Performance Tuning
In-Reply-To: <b918cf3d0502091727267dd57d@mail.gmail.com>
* 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