Re: Profiling a build

[Benny Siegert <bsiegert%netbsd.org@localhost>]

On Tue, 2 Dec 2025, Sad Clouds wrote:

> time ./build.sh

I did that but it only gives me a single value.

> If you need to measure time for individual executables, then you can
> create shell wrappers:
>
> #!/bin/sh
> exec time /usr/bin/gcc.bin "$@" >/dev/null

The problem is that some of these executables are built as part of the 
build and run later. I thought about the wrapper approach but I cannot see 
how to make it work in this case.

> Eliminate disk I/O by building everything on tmpfs file system. Even
> better, create a complete chroot environment on tmpfs, this way you
> avoid most of the disk I/O when loading executables and shared
> libraries.

But the thing is, I want to measure build performance taking into account 
disk I/O and all of that. Also, the amount of RAM is tight already, so I 
cannot afford a ramdisk :/

--
Benny