caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Denis Berthod <casa.berthod@gmail.com>
Cc: Philippe Veber <philippe.veber@gmail.com>,
	caml users <caml-list@inria.fr>
Subject: AW: [Caml-list] Master-slave architecture behind an ocsigen server.
Date: Wed, 27 Mar 2013 23:49:31 +0100	[thread overview]
Message-ID: <1364424571.14693.1@samsung> (raw)
In-Reply-To: <24E57FC8-F2E0-4E4F-9D6B-B8891972A47B@gmail.com>

Am 27.03.2013 23:42:14 schrieb(en) Denis Berthod:
>  Hello,
> 
> Isn't the Lwt_preemptive module exactly what you want?
> 
> http://ocsigen.org/lwt/api/Lwt_preemptive
> 
> But maybe, you want to use real processes and not threads.

In OCaml, only one thread may access runtime functions at a time, and  
because of this, only one thread at a time can run OCaml code. So you  
exploit only one core with a multi-threaded program. I guess this does  
not meet Philippe's scalability requirement, and he wants to use  
processes instead.

Gerd


> Cheers,
> 
> Denis
> 
> Le 26 mars 2013 à 15:29, Philippe Veber a écrit :
> 
> > Dear all,
> >
> > I'm developping an ocsigen website doing some scientific  
> calculations. Up to now, the calculations were done in the same  
> process that runs the server. In order to gain in scalability (and  
> maybe stability too), I would like to run those calculations in a  
> separate (pool of) process(es). As this is a pretty typical setup, I  
> guess quite a few people have already done that. So I'd like to hear  
> some suggestions on what library to use in this particular context.  
> It seems to me that the release library [1] should do the job and is  
> lwt-friendly, but there are maybe other good options?
> >
> > Thanks for any hint, cheers!
> >
> > Philippe.
> >
> > [1] https://github.com/andrenth/release
> 
> 
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs

-- 
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany    gerd@gerd-stolpmann.de
Creator of GODI and camlcity.org.
Contact details:        http://www.camlcity.org/contact.html
Company homepage:       http://www.gerd-stolpmann.de
------------------------------------------------------------

  reply	other threads:[~2013-03-27 22:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 14:29 Philippe Veber
2013-03-26 19:02 ` Martin Jambon
2013-03-26 21:01 ` Martin Jambon
2013-03-27  1:11   ` Francois Berenger
2013-03-28  7:37   ` Philippe Veber
2013-03-28  8:47     ` Alain Frisch
2013-03-28  9:39       ` Philippe Veber
2013-03-28 10:54         ` Alain Frisch
2013-03-28 11:02       ` Anil Madhavapeddy
2013-03-28 11:23         ` Alain Frisch
2013-03-28 12:18         ` AW: " Gerd Stolpmann
2013-03-27 10:00 ` Sébastien Dailly
2013-03-28  8:34   ` Philippe Veber
2013-03-27 16:07 ` Gerd Stolpmann
2013-03-28  9:18   ` Philippe Veber
2013-03-28 12:29     ` AW: " Gerd Stolpmann
2013-03-27 22:42 ` Denis Berthod
2013-03-27 22:49   ` Gerd Stolpmann [this message]
     [not found]     ` <4A6314AA-0C59-4E35-9EA4-F465C0A5AF3A@gmail.com>
2013-03-28  9:23       ` AW: " Philippe Veber

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=1364424571.14693.1@samsung \
    --to=info@gerd-stolpmann.de \
    --cc=caml-list@inria.fr \
    --cc=casa.berthod@gmail.com \
    --cc=gerd@edgespring.com \
    --cc=philippe.veber@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;
as well as URLs for NNTP newsgroup(s).