mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: markw@osdl.org
To: piggin@cyberone.com.au
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
	pgsql-hackers@postgresql.org
Subject: more dbt-2 results hyperthreading on linux-2.6.0-test11
Date: Fri, 12 Dec 2003 14:28:21 -0800 (PST)	[thread overview]
Message-ID: <200312122228.hBCMSOZ28974@mail.osdl.org> (raw)

Hi Nick,

Here are the results of the comparisons I said I would do.

no-hyperthreading:
	http://developer.osdl.org/markw/dbt2-pgsql/282/
	- metric 2288.43
	- baseline

hyperthreading:
	http://developer.osdl.org/markw/dbt2-pgsql/278/
	- metric 1944.42
	- 15% throughput decrease
	
hyperthreading w/ Ingo's C1 patch:
	http://developer.osdl.org/markw/dbt2-pgsql/277/
	- metric 1978.39
	- 13.5% throughput decrease

hyperthreading w/ Nick's w26 patch:
	http://developer.osdl.org/markw/dbt2-pgsql/274/
	- metric 1955.91
	- 14.5% throughput decrease

It looks like there is some marginal benefit to your or Ingo's patches
with a workload like DBT-2.  I probably don't understand enough about
hyperthreading, but I wonder if there's something PostgreSQL can do to
take advantage of hyperthreading

Anyway, each link has pointers to readprofile and annotated oprofile
assembly output (if you find that useful.)  I haven't done enough tests
to have an idea of the error margin, but I wouldn't be surprised if it's
at least 1%.

Let me know if there's anything else you'd like me to try.

Thanks,
Mark

             reply	other threads:[~2003-12-12 22:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12 22:28 markw [this message]
2003-12-12 22:56 Nakajima, Jun
2003-12-12 23:32 ` markw

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200312122228.hBCMSOZ28974@mail.osdl.org \
    --to=markw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pgsql-hackers@postgresql.org \
    --cc=piggin@cyberone.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®