* On 2025年06月26日 at 12:13 BST, Robert Bagdan wrote:
Yeh, to be clear I'm sure it would be faster if I gave it MAKE_JOBS=16, but I can't do that in a bulk build as it would swamp all of the other concurrent builds and make everything else take much longer. Alternatively it could have a very high PBULK_WEIGHT so it starts dead last and get max MAKE_JOBS, but that's still going to end with a significant 8hr+ delay to every build (assuming the build scales perfectly with N cpus, many don't). For quarterly release builds that would be ok, but for daily-ish bulk builds where anything longer runs the risk of the results being obsolete by the time they are posted it's too long. Anyway, as I said, just something that will only be in my bulk builds, and a heads up for anyone reviewing the reports.Just a heads-up that I will be adding NOT_FOR_BULK_PLATFORM=* to my bulk builds for www/chromium. It takes just short of 66 hours(!) to build on my: cpu15: "Intel(R) Xeon(R) CPU E5-2697 v4 @ 2.30GHz" hw.usermem64 = 68678144000I can understand, 66 hours build time is terrible. Just a note: on my i5-4670K, 4 threads, with 24G ram chromium build takes ~18 hours. Without the dependencies, just chromium, but I know it has some heavy dependencies, like llvm, rust, nodejs. The 18 hours is terrible as well, just I'm amazed the 66 hours, as the i5-4790K is weaker than your Xeon.
Cheers, -- Jonathan Perkin pkgsrc.smartos.org Open Source Complete Cloud www.tritondatacenter.com