From: Josh Berkus <josh@agliodbs.com>
To: scott.marlowe <scott.marlowe@ihs.com>
To: Andrew Sullivan <andrew@libertyrms.info>
Cc: pgsql-performance@postgresql.org
Subject: Re: Tuning for mid-size server
Date: Tue, 21 Oct 2003 14:32:16 -0700
Message-ID: <200310211432.16551.josh@agliodbs.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0310211509220.10899-100000@css120.ihs.com>
References: <Pine.LNX.4.33.0310211509220.10899-100000@css120.ihs.com>
Scott,
> I think where it makes sense is when you have something like a report
> server where the result sets may be huge, but the parellel load is load,
> i.e. 5 or 10 users tossing around 100 Meg or more at time.
I've found that that question makes the difference between using 6% & 12% ...
particularly large data transformations ... but not higher than that. And
I've had ample opportunity to test on 2 reporting servers. For one thing,
with very large reports one tends to have a lot of I/O binding, which is
handled by the kernel.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, scott.marlowe@ihs.com, andrew@libertyrms.info
Subject: Re: Tuning for mid-size server
In-Reply-To: <200310211432.16551.josh@agliodbs.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