From: skaller <skaller@users.sourceforge.net>
To: Brian Hurt <bhurt@spnz.org>
Cc: William Lovas <wlovas@stwing.upenn.edu>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] STM support in OCaml
Date: Thu, 09 Mar 2006 09:06:34 +1100 [thread overview]
Message-ID: <1141855594.23909.63.camel@budgie.wigram> (raw)
In-Reply-To: <Pine.LNX.4.63.0603081438460.9569@localhost.localdomain>
On Wed, 2006-03-08 at 14:45 -0600, Brian Hurt wrote:
> One comment I will make is that a mutex is expensive, but not *that*
> expensive. I just wrote a quick program (available if anyone cares) in
> GNU C that measures the cost, in clocks, of locking and unlocking a posix
> mutex. On my desktop box (AMD Athlon XP 2200+ 1.8GHz), I'm getting a cost
> of like 44 clock cycles. Which makes it less expensive than an L2 cache
> miss.
Ahem. Now try that on an AMDx2 (dual core). The cost goes through
the roof if one process has a thread on each core. Because each
core has its own cache and both caches have to be flushed/
synchronised. And those caches are BIG!
I had hoped to compare dual CPU with dual core by buying a
two CPU box (i.e. with two dual cores on it) but they're 2-3
times more expensive because it seems there's no board that
supports Athlons (you need Opterons which cost a lot more).
I have no idea if Linux, for example, running SMP kernel,
is smart enough to know if a mutex is shared between two
processing units or not: AFAIK Linux doesn't support
interprocess mutex. Windows does. Be interesting to
compare.
As mentioned before the only data I have at the moment
is a two thread counter increment experiment on a dual
CPU G5 box, where the speed up from 2 CPUs vs 1 was
a factor of 15 .. times SLOWER.
--
John Skaller <skaller at users dot sourceforge dot net>
Async PL, Realtime software consultants
Checkout Felix: http://felix.sourceforge.net
next prev parent reply other threads:[~2006-03-08 21:38 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 16:18 Asfand Yar Qazi
2006-03-07 16:50 ` [Caml-list] " Sebastian Egner
2006-03-07 17:44 ` Michael Hicks
2006-03-08 0:37 ` Asfand Yar Qazi
2006-03-08 5:05 ` Erick Tryzelaar
2006-03-11 19:43 ` Deadlock free locking scheme (was: Re: [Caml-list] STM support in OCaml) David MENTRE
2006-03-07 17:15 ` [Caml-list] STM support in OCaml skaller
2006-03-07 19:05 ` Asfand Yar Qazi
2006-03-08 0:52 ` skaller
2006-03-08 7:08 ` Bardur Arantsson
2006-03-08 10:38 ` [Caml-list] " Asfand Yar Qazi
2006-03-08 19:36 ` William Lovas
2006-03-08 20:45 ` Brian Hurt
2006-03-08 21:14 ` Paul Snively
2006-03-08 22:06 ` skaller [this message]
2006-03-08 22:10 ` Gerd Stolpmann
2006-03-08 23:48 ` skaller
2006-03-09 7:45 ` Andrae Muys
2006-03-09 9:18 ` David Brown
2006-03-08 22:11 ` Brian Hurt
2006-03-08 23:05 ` Lodewijk Vöge
2006-03-09 3:13 ` Brian Hurt
2006-03-08 23:45 ` Robert Roessler
2006-03-09 0:23 ` skaller
2006-03-09 3:19 ` Brian Hurt
2006-03-09 4:32 ` skaller
2006-03-09 10:38 ` John Chu
2006-03-09 16:53 ` Stefan Monnier
2006-03-11 15:26 ` [Caml-list] " Florian Weimer
2006-03-08 10:11 yoann padioleau
2006-03-08 10:41 ` Asfand Yar Qazi
2006-03-08 12:23 ` skaller
2006-03-08 23:02 ` Asfand Yar Qazi
2006-03-09 0:36 ` skaller
2006-03-08 11:32 ` Gerd Stolpmann
2006-03-08 12:04 ` skaller
2006-03-08 19:22 ` Dan Grossman
2006-03-08 22:10 ` skaller
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=1141855594.23909.63.camel@budgie.wigram \
--to=skaller@users.sourceforge.net \
--cc=bhurt@spnz.org \
--cc=caml-list@yquem.inria.fr \
--cc=wlovas@stwing.upenn.edu \
/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