From: Glyn Astill <glynastill@yahoo.co.uk>
To: david@lang.hm, Steve Clark <sclark@netwolves.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Linux: more cores = less concurrency.
Date: Tue, 12 Apr 2011 17:07:00 +0100 (BST)
Message-ID: <812972.84286.qm@web26008.mail.ukl.yahoo.com> (raw)
In-Reply-To: <4DA41EA5020000250003C6E1@gw.wicourts.gov>
--- On Tue, 12/4/11, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote:
> Wow, zero idle and zero wait, and single digit for
> system. Did you
> ever run those RAM speed tests? (I don't remember
> seeing results
> for that -- or failed to recognize them.) At this
> point, my best
> guess at this point is that you don't have the bandwidth to
> RAM to
> support the CPU power. Databases tend to push data
> around in RAM a
> lot.
I mentioned sysbench was giving me something like 3000 MB/sec on memory write tests, but nothing more.
Results from Greg Smiths stream_scaling test are here:
http://www.privatepaste.com/4338aa1196>
> When I mentioned profiling, I was thinking more of oprofile
> or
> something like it. If it were me, I'd be going there
> by now.
>
Advice taken, it'll be my next step.
Glyn
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: glynastill@yahoo.co.uk, sclark@netwolves.com, Kevin.Grittner@wicourts.gov, jd@commandprompt.com, scott.marlowe@gmail.com
Subject: Re: Linux: more cores = less concurrency.
In-Reply-To: <812972.84286.qm@web26008.mail.ukl.yahoo.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