From: David Rajchenbach-Teller <David.Teller@ens-lyon.org>
To: OCaml <caml-list@inria.fr>
Cc: Nicolas Pouillard <nicolas.pouillard@gmail.com>
Subject: OCamlBuild + OCamlDoc is slooooow
Date: Tue, 10 Mar 2009 23:23:18 +0100 [thread overview]
Message-ID: <1236723798.6458.5.camel@Blefuscu> (raw)
Dear list,
As a number of people on this list have noticed already, the
documentation generation of Batteries Included is awfully slow.
According to our experiments, this is due to the fact that the
combination of ocamlbuild and ocamldoc keeps loading stuff, marshalling
it to the disk and immediately unmarshalling. Alone, this unmarshalling
seems much more costly than all other operations together.
Which brings me to my question: is there a simple way of obtaining the
traditional behaviour of ocamldoc, without this wasteful partial
compilation?
Thanks,
David
--
David Teller-Rajchenbach
Security of Distributed Systems
http://www.univ-orleans.fr/lifo/Members/David.Teller
« Ce matin Un crétin A tué un chercheur. » (air connu)
Latest News of French Research: System being liquidated. Researchers angry.
next reply other threads:[~2009-03-10 22:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 22:23 David Rajchenbach-Teller [this message]
[not found] ` <20090311073040.4fa2461d@alcazar.inria.fr>
2009-03-11 7:40 ` [Caml-list] " David Rajchenbach-Teller
2009-03-11 7:46 ` Maxence Guesdon
2009-03-11 8:03 ` David Rajchenbach-Teller
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=1236723798.6458.5.camel@Blefuscu \
--to=david.teller@ens-lyon.org \
--cc=caml-list@inria.fr \
--cc=nicolas.pouillard@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).