From: "Alexander V. Voinov" <avv@quasar.ipa.nw.ru>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Web Development with OCaml
Date: Tue, 10 Jul 2001 23:03:27 -0700 [thread overview]
Message-ID: <3B4BEC2F.7A3938B7@quasar.ipa.nw.ru> (raw)
In-Reply-To: <3B4BE8CE.B246A7E8@texoma.net>
Hi
Jimmie Houchin wrote:
> The speed and memory results in the shootout are amazing. But what compounds
> it is the LOC result. To me that indicates that a language does not have to be
> verbose to be fast.
...
> Currently fast web servers like Tux 10-15,000+ rps (requests per second),
> Apache 2-4,000 rps aren't dynamic (at those speeds). Dynamic website tools
> like Zope, etc are either like 20-80 rps or some I've seen up to 100-200 rps.
> This is a great disparity.
>
> I want a dynamic website which gets as close to static speeds as possible.
> 3. Tux module. Create an OCaml user space module for Tux.
> This would be interesting and would probably be very fast.
> This is also beyond my skill.
I'd like to seriously wonder about the impact of garbage collection in
such a persistent module, which has to reclaim stuff time to time. And
given that there will be many linked (recursive) data structures, the
process of reclaiming would take time. Unless it may be run as a
separate thread on a separate CPU, and the process of getting space for
new stuff doesn't heavily depend on the collection of the old one (say,
when it's not a problem to malloc one more gig). My suspicion is that
the currently widely discussed shootout doesn't catch the effect of GC.
With all this I mean that you are to maintain a kind of _conceptual_
cache in your dynamic server, like filesystem cache serves for static
pages you mentioned, otherwise it would be little point to apply the
strength of FP. Say, if you store your stuff just in a database, and use
some WebDB, or so, you do not have to bother about FP. (But it all is
complete IMHO)
Alexander
-------------------
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
next prev parent reply other threads:[~2001-07-11 6:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 0:01 Jimmie Houchin
2001-07-10 7:10 ` Jean-Christophe Filliatre
2001-07-10 7:15 ` Tom Hirschowitz
2001-07-10 8:19 ` David Mentre
2001-07-10 9:38 ` Alain Frisch
2001-07-11 5:49 ` Jimmie Houchin
2001-07-11 6:03 ` Alexander V. Voinov [this message]
2001-07-11 14:47 ` Jimmie Houchin
2001-07-12 1:58 ` John Max Skaller
2001-07-11 6:19 ` Alain Frisch
2001-07-11 9:09 ` Samuel Heriard Dubreuil
2001-07-11 14:11 ` Jimmie Houchin
2001-07-11 15:35 ` Francois Rouaix
2001-07-11 20:44 ` Gerd Stolpmann
2001-07-12 2:32 ` Jimmie Houchin
2001-07-13 5:37 ` William Chesters
2001-07-13 10:29 ` Alain Frisch
2001-07-13 11:16 ` Vitaly Lugovsky
2001-07-13 14:04 ` Xavier Leroy
2001-07-13 17:08 ` [web-caml] " Vitaly Lugovsky
2001-07-15 18:03 ` Ari Heitner
2001-07-15 20:19 ` Gerd Stolpmann
2001-07-16 8:23 ` wakita
2001-07-17 16:18 ` John Max Skaller
2001-07-17 18:50 ` Ari Heitner
2001-07-18 22:24 ` John Max Skaller
2001-07-13 16:12 ` Lyn A Headley
2001-07-13 17:50 ` William Chesters
2001-07-13 16:51 ` Miles Egan
2001-07-13 18:12 ` Jimmie Houchin
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=3B4BEC2F.7A3938B7@quasar.ipa.nw.ru \
--to=avv@quasar.ipa.nw.ru \
--cc=caml-list@inria.fr \
/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