Re: Serious performance issues with 1.9.0

[Ludovic Courtès]

Hi,

Martin Ward <address@hidden> writes:

> Now here's something totally wierd with Guile 1.8.7:
>
> echo '(load "ALL.scm")(load "prog_to_spec_TEST.scx")(exit)' | /usr/bin/time 
> guile
>
> takes 139 seconds CPU time.
>
> /usr/bin/time guile -l ALL.scm -s prog_to_spec_TEST.scx
>
> takes only 56 seconds CPU time.

That's expected: in the first case, Guile uses the debugging evaluator,
whereas in the latter it uses the normal (faster) evaluator.

Adding `--no-debug' to the command line of the first one should yield
the same timings as the second one.

> The same thing happens with Guile 1.9.1:
>
> Echo load commands to stdin: 301 seconds CPU time
> Pass the files on the command line: 150 seconds CPU time.
>
> Still nothing appearing in ~/.cache though.

Oh, that's right: it doesn't auto-compile files passed on the
command-line, only modules that are use-module'd it seems.

Not sure whether this is intended, though.  Andy?

You can work around it by manually compiling your source files:

  guile-tools compile -o ALL.go ALL.scm
  ...

The compiled version can then be run with something like:

  guile -c '(load-compiled "ALL.go")'

Can you try this?

Thanks for your perseverance!

Ludo'.