The Raspberry image you were using is based on Alpine and the Fin one on Debian – which are two completely different OSes and is the the most probable cause of the performance difference. Alpine is optimised for size so I wouldn’t be surprised it’s less snappy that a fully performance optimised OS such as Debian.
We initially chose alpine based on this balena blog post. I’m wondering if this is more to do with livepush and local development specifically with Alpine as apposed to the performance of Alpine itself. I’ve cross referenced on our related thread specifically on Livepush performance at Balena-engine crashing during livepush
Thanks all for your help.
Hi Alexander, thanks for bringing it into our attention, and glad to know you are making progress.
About the Alpine blogpost, while still technically correct I often prefer to steer away from Alpine based images (at least while developing). Don’t get me wrong, the size gains are amazing however I’ve found for complex containers where you install multiple packages those gains quickly go away and you start hitting some alpine related problems (less docs and support, and things like this). When developing a container I’ll usually start with debian, then once I’m done I’ll try to “downsize” to alpine if possible and if the image size gains make sense.