Re: why does devel/electron41 show as blacklisted on pkg.f.o

On 6/29/26 12:59, Mark Felder wrote:
> 
> June 24, 2026 at 10:03 PM, "Mark Millard" <[email protected]
> <mailto:[email protected]?
> to=%22Mark%20Millard%22%20%3Cmarklmi%40yahoo.com%3E>> wrote:
> 
>     Do you allow a bunch of other port package builds to potentially be
>     running in parallel?
> 
> 
> Yes, it will often be competing with multiple llvm, gcc, and the rust
> port. But it has never taken anywhere near as long as it does on the
> build cluster.

ALLOW_MAKE_JOBS in use? What sort of figure for the likes of
MAKE_JOBS_NUMBER_LIMIT (or related such) per builder? How many builders
allowed at once? How much RAM? SWAP? (so RAM+SWAP) Style of tmpfs use?

For the most part the official build machines use 3 for
MAKE_JOBS_NUMBER_* type figures as I remember. The maximum builders
count is computed from the RAM and hardware threads available, as I
remember. Using all the hardware threads on some machines would have not
much RAM per hardware thread (mean).

Of the 35000+ port-packages, what size subset do you build (even if only
rarely as large as the figure you give, if you do)?

[The builder machines span a wide range of ages and configurations.]

> 
> Is it because I have 250GB of ccache on an NVME? I wouldn't expect it to
> have such a significant impact but considering the size of the codebase
> perhaps it does.

Could be, depending on how much can be determined to not need
rebuilding. Having an effective NVME ccache spanning a build of 35000+
port packages might be problematical. I'm not aware of the build servers
using such.

-- 
===
Mark Millard
marklmi at yahoo.com