For Amazon Linux, the recipes are slightly different for the AMI versus on-Prem. For the AMI we cut out a bunch of things from the initramfs that you don’t typically need in a cloud environment saving a further second (ish) of launch time. This config is in the Dracula-config-ec2 package.
For on-Prem you may actually use this, so we don’t build it in there.
Amazon Linux 2 is still a supporter OS. When it was released we announced it had 5 years of LTS support. With the AL2022 preview, we have just announced what comes after AL2.
AL2 is less of a rolling release than AL1 was. AL1 had a new release every six months.
What this practically means is that a plain "make -j" will spawn all the processes that could run concurrently. So if you're building 1,000 files, it'll spawn 1,000 processes. This can either be fine, or completely terrible, depending on the number of CPUs you have an the amount of memory each process uses.
Not just Macs, plenty of Linux systems have a big.LITTLE design.
with a big.LITTLE system it'll really depend what you're doing. Just compiling something? It's probably fine (if all cores can be active at once). If you're wanting more consistent performance for some calculations? You might need to think a bit more.
I wasn't talking about the reading of the number of CPUs you could use, but rather how many threads you'd spawn based on that information.
There may be 10 CPUs in the machine, but if your in your container which is restricted to using only 1 of them, it's no use launching 10 threads in that container over just having one.
For on-Prem you may actually use this, so we don’t build it in there.