From: skaller <skaller@users.sourceforge.net>
To: Asfand Yar Qazi <email@asfandyar.cjb.net>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] STM support in OCaml
Date: Wed, 08 Mar 2006 23:23:05 +1100 [thread overview]
Message-ID: <1141820585.20944.550.camel@budgie.wigram> (raw)
In-Reply-To: <440EB4C2.2080102@asfandyar.cjb.net>
On Wed, 2006-03-08 at 10:41 +0000, Asfand Yar Qazi wrote:
> Also, from what I remember, STM is "optimistic", while conventional lock-based
> design is "pessimistic" - thereby allowing STM based code to spend less time
> checking for locks or something, which apparently makes it quicker.
> But, I'll lets the experts explain it :-)
It isn't explanation that is needed but experience
actually using it. The performance tradeoffs -- including
developer time -- won't be evident until significant
applications are developed using it.
For example I wonder if the technique is worthwhile
*without* the Haskell type system to enforce correctness?
And given GHC is currently not generating very good code,
will it matter anyhow?
--
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 12:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 10:11 yoann padioleau
2006-03-08 10:41 ` Asfand Yar Qazi
2006-03-08 12:23 ` skaller [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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-07 17:15 ` skaller
2006-03-07 19:05 ` Asfand Yar Qazi
2006-03-08 0:52 ` skaller
2006-03-08 10:38 ` 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
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-11 15:26 ` Florian Weimer
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=1141820585.20944.550.camel@budgie.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@yquem.inria.fr \
--cc=email@asfandyar.cjb.net \
/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