From: Scott Marlowe <scott.marlowe@gmail.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Bob Dusek <redusek@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: performance config help
Date: Mon, 11 Jan 2010 12:38:42 -0700
Message-ID: <dcc563d11001111138t5a2003b8j736e9f5beacf7636@mail.gmail.com> (raw)
In-Reply-To: <dcc563d11001111136y117ea68dp651fd24ce72385f3@mail.gmail.com>
References: <4B4B177B020000250002E194@gw.wicourts.gov>
<dcc563d11001111136y117ea68dp651fd24ce72385f3@mail.gmail.com>
On Mon, Jan 11, 2010 at 12:36 PM, Scott Marlowe <scott.marlowe@gmail.com> wrote:
> FYI, on an 8 or 16 core machine, 10k to 30k context switches per
> second aren't that much. If you're climbing past 100k you might want
> to look out.
>
> The more I read up on the 74xx CPUs and look at the numbers here the
> more I think it's just that this machine has X bandwidth and it's
> using it all up. You could put 1,000 cores in it, and it wouldn't go
> any faster. My guess is that a 4x6 core AMD machine or even a 2x6
> Nehalem would be much faster at this job. Only way to tell is to run
> something like the stream benchmark and see how it scales,
> memory-wise, as you add cores to the benchmark.
Also I'm guessing that query profiling may help, if we can get the
queries to request less data to trundle through then we might be able
to get Bob the performance needed to keep up.
But at some point he's gonna have to look at partitioning his database
onto multiple machines some how.
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: scott.marlowe@gmail.com, Kevin.Grittner@wicourts.gov, redusek@gmail.com
Subject: Re: performance config help
In-Reply-To: <dcc563d11001111138t5a2003b8j736e9f5beacf7636@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