From: "Jérémie Dimino" <jeremie@dimino.org>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Asynchronous IO programming in OCaml
Date: Wed, 27 Oct 2010 17:30:26 +0200 [thread overview]
Message-ID: <20101027153026.GD32282@aurora> (raw)
In-Reply-To: <877hh33g52.fsf@frosties.localdomain>
On Wed, Oct 27, 2010 at 03:43:37PM +0200, Goswin von Brederlow wrote:
> But then you tune your benchmark to give you the result you want instead
> of benchmarking what normaly happens.
That's true for read or write. The point i wanted to make is that in the
general case, i.e. for a system call that blocks, wrapping it into a
thread might not be a good solution because it degrades performances too
much.
> And don't forget. Multi core systems are more and more widely
> spread. What is wrong with 2 cores doing memcpy twice as fast?
I don't think you can read or write in parallel the RAM with current
architectures, but i may be wrong.
> Do you have a different solution for writes that will avoid threads when
> a write won't block? And how do you restart jobs once the data has
> actually been commited to disk? (i.e. how do you do fsync()?)
Unfortunately no, we have no solution for write. The main problem i see
with doing write in parallels with threads is to handle errors.
Jérémie
next prev parent reply other threads:[~2010-10-27 15:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 10:34 Jon Harrop
2010-10-24 12:51 ` [Caml-list] " philippe
2010-10-24 12:52 ` Dario Teixeira
2010-10-24 16:33 ` oliver
2010-10-24 18:50 ` Dario Teixeira
2010-10-24 19:04 ` bluestorm
2010-10-24 20:02 ` oliver
2010-10-24 21:51 ` Michael Ekstrand
2010-10-24 16:17 ` Jake Donham
2010-10-24 20:54 ` Anil Madhavapeddy
2010-10-24 22:50 ` Jérémie Dimino
2010-10-25 3:42 ` Markus Mottl
2010-10-25 7:49 ` Richard Jones
2010-10-25 8:42 ` Goswin von Brederlow
2010-10-25 11:10 ` Jérémie Dimino
[not found] ` <AANLkTimP77PDEChW3Yt6uUy_qxYpj6EOZWQ_==id-LBC@mail.gmail.com>
[not found] ` <20101025143317.GB32282@aurora>
2010-10-25 15:34 ` Yaron Minsky
2010-10-25 17:26 ` Jérémie Dimino
2010-10-27 9:33 ` Goswin von Brederlow
2010-10-27 11:18 ` Jérémie Dimino
2010-10-27 13:43 ` Goswin von Brederlow
2010-10-27 15:30 ` Jérémie Dimino [this message]
2010-10-28 9:00 ` Goswin von Brederlow
2010-10-28 9:28 ` Jérémie Dimino
2010-10-28 10:11 ` Goswin von Brederlow
2010-10-25 15:58 ` DS
2010-10-24 20:42 ` Goswin von Brederlow
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=20101027153026.GD32282@aurora \
--to=jeremie@dimino.org \
--cc=caml-list@inria.fr \
--cc=goswin-v-b@web.de \
/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;
as well as URLs for NNTP newsgroup(s).