My team is using the balenalib/rpi-raspbian:stretch and balenalib/rpi-raspbian:buster images as builder images that are used to build omnibus-gitlab packages for Raspbian. I noticed while adding buster support that configuring and compiling the software (git, ruby) on buster takes more time than stretch.
Here are some timing profiles I’ve:
|stretch, gcc 6.3.0||90min|
|stretch, gcc 8.3.0||136min|
|buster, gcc 8.3.0||207min|
|buster, gcc 9.2.1||236min|
I expect compilation time to take longer when using QEMU as the balenalib Docker images do, but it’s not clear why the buster image takes more time than stretch to build the same software. Anyone run into this before?