Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Richard Jones <rich@annexia.org>
To: Markus Mottl <markus.mottl@gmail.com>
Cc: "Jérémie Dimino" <jeremie@dimino.org>,
	"Jon Harrop" <jon@ffconsultancy.com>,
	caml-list@yquem.inria.fr, "Anil Madhavapeddy" <anil@recoil.org>
Subject: Re: [Caml-list] Asynchronous IO programming in OCaml
Date: Mon, 25 Oct 2010 08:49:54 +0100	[thread overview]
Message-ID: <20101025074954.GA25619@annexia.org> (raw)
In-Reply-To: <AANLkTin-JsN0JgFYzZHNT1C_wmwXzCgfV-+8XeQqMk4O@mail.gmail.com>

On Sun, Oct 24, 2010 at 11:42:45PM -0400, Markus Mottl wrote:
> On Sun, Oct 24, 2010 at 18:50, Jérémie Dimino <jeremie@dimino.org> wrote:
> > 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.
> 
> The performance of select was also usually slightly better in my
> experiments than with epoll for at least a few tens of descriptors.
> It really depends on what your requirements are.  If you are facing
> hundreds or even thousands of connections, you'll probably want to
> consider epoll.  select does not scale well.

I think if you really had 10,000 clients per server you'd probably
want to consider your whole architecture.  Putting nginx or a very
cut-down Apache on the front and memcached between the webserver and
the database.

Rich.

-- 
Richard Jones
Red Hat


  reply	other threads:[~2010-10-25  7:49 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 [this message]
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=20101025074954.GA25619@annexia.org \
    --to=rich@annexia.org \
    --cc=anil@recoil.org \
    --cc=caml-list@yquem.inria.fr \
    --cc=jeremie@dimino.org \
    --cc=jon@ffconsultancy.com \
    --cc=markus.mottl@gmail.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