From: skaller <skaller@users.sourceforge.net>
To: Thomas Fischbacher <tf@functionality.de>
Cc: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>,
sds@gnu.org, caml-list@inria.fr
Subject: Re: [Caml-list] Re: compiling large file hogs RAM and takes a long time.
Date: Fri, 08 Jun 2007 19:35:53 +1000 [thread overview]
Message-ID: <1181295353.20252.26.camel@rosella.wigram> (raw)
In-Reply-To: <46691BE3.1050607@functionality.de>
On Fri, 2007-06-08 at 10:05 +0100, Thomas Fischbacher wrote:
> skaller wrote:
>
> > You mention in the ticket there is a hard way out .. using
> > binary trees; hard because it would require changes everywhere
> > in the compiler. Is this actually enough? Seems to reduce
> >
> > O(n * n * log n)
> >
> > to
> >
> > O( n * log n * log n)
> >
> > which is still pretty bad.. is that right?
>
> What would be so bad about O(n log n log n)?
> After all, in our relevant computing universe, there
> always is an upper bound to log n which is quite
> a small constant (like 25 or so).
Perhaps you're right .. still, there's a big difference
between a 5 minute compile (enough time to make a coffee!)
and a 2 hour compile (enough time to have lunch!)
I just went through this: Felix normal build time is
about 20 minutes including all tests. With an early version
of Dypgen parser, this was changed to around 4 hours...
luckily, back to 20 minutes now. Even a small % increase
in times can be quite significant.
I usually illustrate this by asking if you'd be happy
to give up your 2 / 52 week annual holiday .. that's
under 4% of the year.. I'm sure you'd be horrified ..
4% is a LOT!
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2007-06-08 9:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 16:30 Sam Steingold
2007-06-06 16:51 ` [Caml-list] " skaller
2007-06-06 17:05 ` Sam Steingold
2007-06-07 15:52 ` Sam Steingold
2007-06-08 1:02 ` [Caml-list] " Jacques Garrigue
2007-06-08 1:51 ` skaller
2007-06-08 2:26 ` Yaron Minsky
2007-06-08 9:05 ` Thomas Fischbacher
2007-06-08 9:35 ` skaller [this message]
2007-06-08 9:55 ` Thomas Fischbacher
2007-06-08 13:39 ` Sam Steingold
2007-06-08 12:30 ` [Caml-list] " Jacques Garrigue
2007-06-15 15:41 ` Sam Steingold
2007-06-15 18:56 ` [Caml-list] " Jon Harrop
2007-06-15 20:06 ` Sam Steingold
2007-07-09 20:22 ` large parametrized polymorphic variant type combinations take forever to compile Sam Steingold
2007-07-09 22:45 ` Sam Steingold
2007-07-09 23:37 ` [Caml-list] " Jacques Garrigue
2007-07-10 7:09 ` Christophe Raffalli
2007-07-10 7:31 ` Jacques Garrigue
2007-07-10 14:16 ` Sam Steingold
2007-07-10 16:49 ` Sam Steingold
[not found] ` <46938BDA.1090605@podval.org>
2007-07-11 0:10 ` [Caml-list] " Jacques Garrigue
2007-07-11 1:19 ` Jon Harrop
2007-07-11 2:23 ` Jacques GARRIGUE
2007-07-11 13:12 ` Sam Steingold
2007-07-11 19:17 ` [Caml-list] " Jon Harrop
2007-07-10 3:34 ` [Caml-list] " skaller
2007-07-10 13:27 ` Sam Steingold
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=1181295353.20252.26.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=garrigue@math.nagoya-u.ac.jp \
--cc=sds@gnu.org \
--cc=tf@functionality.de \
/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