From: Glyn Astill <glynastill@yahoo.co.uk>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Linux: more cores = less concurrency.
Date: Mon, 11 Apr 2011 20:42:46 +0100 (BST)
Message-ID: <356731.11980.qm@web26005.mail.ukl.yahoo.com> (raw)
In-Reply-To: <BANLkTik2+T3xmpStJNVxWzXQWgxU14bVeA@mail.gmail.com>
--- On Mon, 11/4/11, Scott Marlowe <scott.marlowe@gmail.com> wrote:
> Just FYI, in synthetic pgbench type benchmarks, a 48 core
> AMD Magny
> Cours with LSI HW RAID and 34 15k6 Hard drives scales
> almost linearly
> up to 48 or so threads, getting into the 7000+ tps
> range. With SW
> RAID it gets into the 5500 tps range.
>
I'll have to try with the synthetic benchmarks next then, but somethings definately going off here. I'm seeing no disk activity at all as they're selects and all pages are in ram.
I was wondering if anyone had any deeper knowledge of any kernel tunables, or anything else for that matter.
A wild guess is something like multiple cores contending for cpu cache, cpu affinity, or some kind of contention in the kernel, alas a little out of my depth.
It's pretty sickening to think I can't get anything else out of more than 8 cores.
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, scott.marlowe@gmail.com, Kevin.Grittner@wicourts.gov, jd@commandprompt.com
Subject: Re: Linux: more cores = less concurrency.
In-Reply-To: <356731.11980.qm@web26005.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