From: "Jérémie Dimino" <jeremie@dimino.org>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: Jake Donham <jake@donham.org>, Jon Harrop <jon@ffconsultancy.com>,
caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Asynchronous IO programming in OCaml
Date: Mon, 25 Oct 2010 00:50:37 +0200 [thread overview]
Message-ID: <20101024225037.GA8999@aurora> (raw)
In-Reply-To: <A7C6ED92-10BA-444B-A381-FC6AB7666932@recoil.org>
On Sun, Oct 24, 2010 at 01:54:50PM -0700, Anil Madhavapeddy wrote:
> This should work fine for a couple of thousand clients or so, but you'll
> begin to see degradation as the number of clients increase. This is
> because LWT internally uses select(2) to wait for file-descriptors, and
> not the newer kqueue(2) or epoll(2) interfaces. You can read more about
> the "C10K problem" here: [3]http://www.kegel.com/c10k.html
> I've got a stripped-down version of LWT that uses these newer event-driven
> kernel interfaces (and so should be able to cross the 10,000 client
> barrier fairly easily), but it won't be ready for release for another
> month or so. Drop me an email off-list if you want to try it out earlier.
I made an implementation of lwt using libev [1]. I tested it with
ocsigen and ab but the result was always a bit better with select than
with epoll. That is why i did not replace select by libev in the main
branch. In fact i never found the source of any benchmark comparing
select to epoll on the web.
> Async disk I/O under Linux is annoyingly problematic if you aren't using
> direct I/O (and hence page/block-aligned structures). Avoid if possible :)
The next version of Lwt will support asynchronous disk I/O by using
mincore + mmap. It is already in the development version.
Jérémie
[1] http://www.dimino.org/cgi-bin/darcsweb.cgi?r=lwt-libev;a=summary
next prev parent reply other threads:[~2010-10-24 22:51 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 [this message]
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
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=20101024225037.GA8999@aurora \
--to=jeremie@dimino.org \
--cc=anil@recoil.org \
--cc=caml-list@yquem.inria.fr \
--cc=jake@donham.org \
--cc=jon@ffconsultancy.com \
/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