Hello,
I would like to collect information about the time it takes to compile
an ASDF system (possibly also load it), dependencies excluded. I'm
thinking there's probably a way to do this by :around'ing compile-op, or
something like that, but if someone already has a clear view on how to
make
> Hello,
>
> I would like to collect information about the time it takes to compile
> an ASDF system (possibly also load it), dependencies excluded. I'm
> thinking there's probably a way to do this by :around'ing compile-op, or
> something like that, but if someone already has a clear view on how
François-René ÐVB Rideau écrivait:
> Simplest method:
> 1- load the dependencies, possibly using (asdf:operate :prepare-op s)
> 2- (time (asdf:make s))
Nice, thank you. If I want to time separately the compilation and
loading phases of several libraries (which may depend on each other)
how
On 5 Dec 2018, at 9:46, Didier Verna wrote:
François-René ÐVB Rideau écrivait:
Simplest method:
1- load the dependencies, possibly using (asdf:operate :prepare-op s)
2- (time (asdf:make s))
Nice, thank you. If I want to time separately the compilation and
loading phases of several libra
"Robert Goldman" écrivait:
> Depending on the host lisp you are using, couldn't you wrap the calls
> to COMPILE-FILE and LOAD in code that times those operation?
I could, but since I want per-library numbers, I would need to
reconstruct that information afterwards...
--
Resistance is futil
On 5 Dec 2018, at 10:04, Didier Verna wrote:
"Robert Goldman" écrivait:
Depending on the host lisp you are using, couldn't you wrap the calls
to COMPILE-FILE and LOAD in code that times those operation?
I could, but since I want per-library numbers, I would need to
reconstruct that info
"Robert Goldman" écrivait:
> This is yet another problem that comes from the fact that the build
> plans are linear, instead of hierarchical -- for example there's no
> subsequence that is identifiable as being the set of operations for a
> particular module.
>
> Logically speaking, there's a tre
