From: Florian Weimer <fweimer@bfk.de>
To: Willo van der Merwe <willo@mirasol.co.za>
Cc: Jean-David Beyer <jeandavid8@verizon.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hardware spec
Date: Thu, 06 Sep 2007 16:19:03 +0200
Message-ID: <82k5r3op0o.fsf@mid.bfk.de> (raw)
In-Reply-To: <46DFE674.6060702@mirasol.co.za>
References: <46DFA43C.2030201@mirasol.co.za>
<46DFB79E.9040407@archonet.com>
<46DFC7D6.2080803@mirasol.co.za>
<46DFE170.20206@verizon.net>
<46DFE674.6060702@mirasol.co.za>
* Willo van der Merwe:
> Good advice. After running a vmstat and iostat, it is clear, to my
> mind anyway, that the most likely bottleneck is IO, next is probably
> some more RAM.
> Here's the output:
> procs -----------memory---------- ---swap-- -----io---- --system--
> ----cpu----
> r b swpd free buff cache si so bi bo in cs us
> sy id wa
> 0 0 29688 80908 128308 3315792 0 0 8 63 6 8 17
> 2 80 1
You need to run "vmstat 10" (for ten-second averages) and report a
couple of lines.
> avg-cpu: %user %nice %sys %iowait %idle
> 17.18 0.00 1.93 0.81 80.08
Same for iostat.
Your initial numbers suggest that your server isn't I/O-bound, though
(the percentage spent in iowait is much too small, and so are the tps
numbers).
--
Florian Weimer <fweimer@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
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: fweimer@bfk.de, willo@mirasol.co.za, jeandavid8@verizon.net
Subject: Re: Hardware spec
In-Reply-To: <82k5r3op0o.fsf@mid.bfk.de>
* 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