caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
* [Caml-list] Will Ocaml use a  4-way SMP box without splitting the program into separate processes?
@ 2001-07-13 19:59 Mattias Waldau
  2001-07-15 11:32 ` Xavier Leroy
  0 siblings, 1 reply; 5+ messages in thread
From: Mattias Waldau @ 2001-07-13 19:59 UTC (permalink / raw)
  To: Caml list

As I understand it, Ocaml has one master lock for handling threading.

Doesn't this mean that a process can never use more than one processor?

And if that is true, following Xavier Leroy idea "Using
separate processes for the HTTP server/servlet container and for the
servlets (but not starting a new servlet process on each request like
CGI does)" is the only scalable way to go.

Because, I don't think a solution that doesn't use a SMP-machine effectively
is a good solution.

> [mailto:owner-web-caml@quatramaran.ens.fr]On Behalf Of William Chesters
> Depends on the kind of market you are thinking of.  The performance we
> get out of Melati+postgres on a cheap PC is adequate for the great
> majority of all known websites, without really trying.  If you put a
> good ocaml-based equivalent on a 4-way SMP box talking to a database
> on another box, you would be comfortably into the hundreds of hits per
> second I reckon.

What have I misunderstood?

/mattias

-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2001-07-20 14:02 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-07-13 19:59 [Caml-list] Will Ocaml use a 4-way SMP box without splitting the program into separate processes? Mattias Waldau
2001-07-15 11:32 ` Xavier Leroy
2001-07-15 12:15   ` William Chesters
2001-07-17  1:59   ` Alexander V. Voinov
2001-07-20 14:01     ` Xavier Leroy

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).