Re: Speeding up the bulk build scan phase

[Jonathan Perkin <jperkin%pkgsrc.org@localhost>]

* On 2026-01-15 at 15:30 GMT, Thomas Klausner wrote:

> I've just got rid of two more forks in mk/compiler/gcc.mk, and with
> that and setting PBULK_CACHE_DIRECTORY to an empty directory, a full
> bulk build scan (using bob) is now down to 3m38s in a test run I just
> did.

You'll also be benefiting from a change I pushed to bob trunk that now 
execs bmake directly for scans rather than going via a shell:

  https://github.com/jperkin/bob/commit/02cecffe2a9d684afa5d028adc7ec1f3e934c1c0

On my 2021 laptop I'm now down to a full scan from scratch in 2m 30s.

> It would actually be nice if pbulk/bob handled this setting
> automatically, i.e. set the variable to a temporary directory (only
> used during the scan phase, or perhaps even during the build phase,
> but there the speedup will be less noticeable) and remove it after the
> bulk build finishes.

My worry about doing this is that it would override any setting that the 
user has for PBULK_CACHE_DIRECTORY in mk.conf.  I've personally been 
setting it since:

  commit 8329489d7a2e947ccee28402421d030f8477a325
  Author: Jonathan Perkin <jperkin%joyent.com@localhost>
  Date:   Tue Dec 27 11:25:15 2016 +0000

      Set PBULK_CACHE_DIRECTORY for supported branches.

and this would go against my goal for principle-of-least-astonishment.  
I will likely instead just ensure that it is prominently documented in 
the examples.

--
Jonathan Perkin                    pkgsrc.smartos.org
Open Source Complete Cloud   www.tritondatacenter.com