From: "Richard W.M. Jones" <rich@annexia.org>
To: SerP <serp256@gmail.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Very slow compilation
Date: Tue, 13 Mar 2012 16:58:05 +0000 [thread overview]
Message-ID: <20120313165805.GC23811@annexia.org> (raw)
In-Reply-To: <CAHgca+_m7iw8iFDb+23m3UgWMFM5j__ctY3o1oTyJ-HKP_57yQ@mail.gmail.com>
On Sun, Mar 11, 2012 at 12:11:51PM +0400, SerP wrote:
> We encountered a problem of a slow compilation. When the project grew up,
> the time of compilation increased considerably. We have many classes and
> objects, and the type checking of objects and classes performs very slowly.
> I have Core i3 3GHz iMac, and the average compilation time of one module is
> 7-13 seconds. The entire projet is compiled within 10-15 minutes. The major
> part of the time is taken by "Typemod.type_implementation", which include
> many calls of Ctype.unify (80% of compilation time). Now, it is getting
> hard and slow to develop the projetct, are there any ways to accelarate it?
> It is difficult to get all fine points, but I wish I could make the process
> faster. Thanks for any help or comments. Looking forward to your reply
I have seen slow compilation with OCaml, but for me it only happened
for very large (generated) source files, about 60,000 lines of code.
Avoiding very large source files may help.
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2012-03-13 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 8:11 SerP
2012-03-11 8:39 ` Gabriel Scherer
2012-03-11 9:04 ` Adrien
2012-03-11 9:21 ` Raphael Proust
2012-03-13 22:02 ` Matti Jokinen
2012-03-13 22:46 ` Gerd Stolpmann
2012-03-14 5:33 ` Gabriel Scherer
2012-03-14 8:52 ` Pierre Chambart
2012-03-13 16:58 ` Richard W.M. Jones [this message]
2012-03-14 14:45 tools
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=20120313165805.GC23811@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=serp256@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