Re: Installing Signal
- Reply: D'Arcy Cain : "Re: Installing Signal"
- In reply to: Henrik Morsing : "Re: Installing Signal"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 11 Aug 2024 10:41:46 UTC
On 8/11/24 01:33, Henrik Morsing wrote: >> Hi Henrik, >> >> on my server it takes around 36 hours the first time. I think electron >> actually takes most of that, if I remember correctly. >> >> I guess that's why it's removed from packages. >> > > Thanks, that's good to know. I will perservere. > > I'm on an i5-12600KF with DDR4 memory and NVMe disk. > > I tried running make with -j but that instantly bombed out with an > error. No idea why, I didn't think that would ever not work. Unless anything has changed, the FreeBSD ports tree is not compatible with -j to make it do its work in parallel. Doing so will cause parallelization like multiple dependencies to be built at once. It is supported to have parallelization within a single port (which will carry out to dependencies, but one at a time). Replace -j# with MAKE_JOBS_NUMBER=# to get that effect. Ports can define DISABLE_MAKE_JOBS to disable this when they are known to have issues building with multiple jobs and some ports don't have/use make which can impact if there is any parallelization available. If you insist on trying to build multiple ports at the same time in an automated fashion then you would want to try poudriere (no experience with synth to know if it does it too). In addition to being able to define MAKE_JOBS_NUMBER= (which defaults to 1 on poudriere) you can set PARALLEL_JOBS=# in poudriere's configuration file (defaults to cpu count) or define it with -J# as a parameter to the executed poudriere command. Due to the default '1' job per port, its not uncommon that users either need to lengthen the timeout or increase the job count for some larger ports. I find it a much more efficient use of resources to have fewer, but still multiple, parallel jobs while having jobs within a port number increased which helps minimize storage space while still keeping CPU 'usually' busy; CPU will not always be maxed when it could be if a either job count is only 1 and overcommitting CPU cores has been able to finish build jobs even faster but does impact system responsiveness more. > Regards, > Henrik Morsing >