Time trace large amounts of time spent in writing of files about ldc HOT 8 CLOSED

That time trace comes from https://github.com/ldc-developers/ldc/blob/master/driver/toobj.cpp#L385 I'm not sure what any more granularity you would reasonably get more information from, assuming that you are just writing object files xor LLVM bitcode.

Have you tried using object cacheing (--cache=<cache dir>)?

from ldc.

I haven't tried caching.

However, there certainly is more granularity left i.e. linking isn't measured. Plus there could be a "and everything else after write" stage.

from ldc.

That function only does object file writing, not linking. There is a time trace-point https://github.com/ldc-developers/ldc/blob/master/driver/linker.cpp#L292 for linking. Is that insufficient?

from ldc.

Very insufficient.

tt.txt

from ldc.

all the rest of that is LLVM though, I'm not sure there in much we can do. and that is with to without cache?

from ldc.

Ths is LLVM codegen. IIRC, the first version of -ftime-trace did include the LLVM traces too, but Johan then rewrote it so that we only have LDC's own traces.

from ldc.

Turning on cache does indeed allow non-clean builds to be sped up significantly thanks!

However, I do think that something isn't right with it taking that long.
Without additional measurements there is no way to know what is causing it.

I'll close for now.

from ldc.

Ths is LLVM codegen. IIRC, the first version of -ftime-trace did include the LLVM traces too, but Johan then rewrote it so that we only have LDC's own traces.

This.

We can't (yet) easily hook into LLVM's timetracing together with LDC's own...

from ldc.