On Thu, Sep 23, 2021 at 8:37 AM Janne Johansson <[email protected]> wrote:
> Could this handwaving please stop? If anyone wants, make a i386 VM and > do a binary search and record the minimums. > I have done this exercise, but not for kernel relinking -- it was for doing full system rebuilds. Starting with 2.0/i386 I made a VM with 64MB RAM and a 4GB disk, then tried to do a full rebuild of -stable. If the build quit with an error I'd increase the RAM and if the file system filled I'd up the disk space. Then I'd make a new VM for the next release, starting with the minimum RAM and disk required for the previous one (i.e. if requirements had *dropped* dramatically from one release to the next I wouldn't have noticed). For 6.9/i386, 512MB RAM and 512MB swap are sufficient. With 256MB RAM builds may fail. This minimum appears to have taken effect in 6.8/i386. I have not done this test for 7.0 yet, but I was having trouble getting builds to run to completion with only 512MB RAM in -current in February 2021. If this wasn't a temporary thing in -current, I would expect the minimum in 7.0/i386 to be 1GB RAM / 512MB swap. If anyone cares, for 6.2/i386 through 6.7 256MB RAM and 512MB swap is sufficient. For 4.8 through 6.1, 128MB RAM / 512MB swap was enough. amd64 has needed 1GB RAM and 1GB swap to do full system rebuilds since 6.6. For 6.3 through 6.5, 512MB RAM and 1GB swap is sufficient. 6.2 will build with 512MB RAM and 512MB swap. 4.8 through 6.1 will build with 256MB RAM and 512MB swap. 4.4 through 4.7 will build with 128MB RAM and 512MB swap. If it matters, all of this testing was done on an old Dell PowerEdge 2900 III server with dual Xeon E5450 processors and 48GB RAM, running VMware ESXi 5.5 Update 2. All VMs were "version 8" guests in VMware, and all VMs were configured with 1 virtual cpu socket with 1 virtual core until release 3.5, then changed to 1 socket / 2 cores for 3.6 and later releases. -ken
