pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Claudio Freire <klaussfreire@gmail.com>
Cc: sthomas@optionshouse.com, Craig James <cjames@emolecules.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hyperthreading (was: Two identical systems, radically different performance)
Date: Wed, 10 Oct 2012 11:46:03 -0400
Message-ID: <20121010154603.GA11892@momjian.us> (raw)
In-Reply-To: <CAGTBQpY8Fb5Un7w2LjP0i1qfvP3Qiqu=weyGkXmehExfXAbL7g@mail.gmail.com>
References: <CAFwQ8revW5Ez6uCUqPeUFVHh0pdy0OZKv8_nM0SvxHgTM055EQ@mail.gmail.com>
	<CAFwQ8re9O2Nvao3UsUxDxFZZUsoSqNJSC4jaKGB9cJ7_YyjoBA@mail.gmail.com>
	<50756F95.7040006@optionshouse.com>
	<CAGTBQpY8Fb5Un7w2LjP0i1qfvP3Qiqu=weyGkXmehExfXAbL7g@mail.gmail.com>

On Wed, Oct 10, 2012 at 11:44:50AM -0300, Claudio Freire wrote:
> On Wed, Oct 10, 2012 at 9:52 AM, Shaun Thomas <sthomas@optionshouse.com> wrote:
> > On 10/09/2012 06:30 PM, Craig James wrote:
> >
> >>                ra:8192 walb:1M   ra:256 walb:1M    ra:256 walb:256kB
> >>                ----------------  ----------------  -----------------
> >> -c  -t        Run1  Run2  Run3  Run4  Run5  Run6  Run7  Run8  Run9
> >> 40  2500      4261  3722  4243  9286  9240  5712  9310  8530  8872
> >> 50  2000      4138  4399  3865  9213  9351  9578  8011  7651  8362
> >
> >
> > I think I speak for more than a few people here when I say: wat.
> >
> > About the only thing I can ask, is: did you make these tests fair? And by
> > fair, I mean:
> >
> > echo 3 > /proc/sys/vm/drop_caches
> > pg_ctl -D /your/pg/dir restart
> 
> Yes, I was thinking the same. Especially if you check the tendency to
> perform better in higher-numbered runs. But, as you said, that doesn't
> explain that jump to twice the TPS. I was thinking, and I'm not
> pgbench expert, could it be that the database grows from run to run,
> changing performance characteristics?
> 
> > My head hurts.
> 
> I'm just confused. No headache yet.
> 
> But really interesting numbers in any case. It these results are on
> the level, then maybe the kernel's read-ahead algorithm isn't as
> fool-proof as we thought? Gotta read the source. BRB

Well, I have exactly the same setup here:

	new: 2x4-core Intex Xeon E5620 2.40 GHz

Let me know if you want any tests run, on SSDs or magnetic disk.  I do
have hyperthreading enabled, and Greg Smith benchmarked my server and
said it was good.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +




view thread (11+ messages)  latest in thread

Message-ID: <20121010154603.GA11892@momjian.us>
Permalink:  ../20121010154603.GA11892@momjian.us/
Also on:    postgresql.org/message-id/20121010154603.GA11892@momjian.us

 · 

reply

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: bruce@momjian.us, klaussfreire@gmail.com, cjames@emolecules.com
  Subject: Re: Hyperthreading (was: Two identical systems, radically different performance)
  In-Reply-To: <20121010154603.GA11892@momjian.us>

* 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