Lyn A Headley writes:
 > I'd also like to make a point in passing.  Dynamic web development
 > performance has less to do with the implementation language of the web
 > application than it does with the database backend and associated
 > indexes, and with your caching and concurrency strategy.

That has been our experience with Melati; one can easily end up
database-bound---or more likely waiting on the staggeringly slow
JDBC driver (try postgresql's some time ...).

Melati's cacheing can be very helpful.  But of course concurrency
tends to work against cacheing ...

 > I believe, if performance is a main concern, that you will have to
 > commit deep thought to those issues especially.

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