![]() ![]() We then asked teams across the organisation to make sure dependencies and relevant tooling were accurately updated. We set up a workstream dedicated to assist our developers while in the process of reaching full support. To enable this upgrade, we needed to add support for the new machines to our development infrastructure. How does one prioritise and scale in a distributed-first world? ![]() Were the machines actually better in build time performance? And was the performance improvement worth the investment required to procure the machines?īased on the empirical findings and our financial analysis, upgrading to Apple silicon machines definitely meets our criteria and is a viable solution to reduce developer build time woes. We had two questions to answer to be completely satisfied. In our analysis, we found the upgrade to be cost-effective as well - we break even in about three months, and we could potentially save up to 36% in engineering costs per team. Are there any financial benefits in upgrading to M1s? Overall: Apple silicon is about 43% faster.Īndroid: Apple silicon is about 50% faster. Given the processing capabilities of M1s, we hypothesised that M1 machine local build times would improve significantly.ĪvgLocalBuildTime(M1) < AvgLocalBuildTime(non-M1) Empirical findings *What is “good enough”? For the purpose of our analysis, we define “good enough” as a statistically significant performance improvement in Android/iOS local build times. ![]() Will the performance improvements justify the monetary investment required?.Do we have machines good enough* to be used by Spotify developers?.Our problem statement can be summarised in two points: A wonderful blog post by a Reddit staff engineer inspired us not to stop at just system performance, but also to validate a financial use case for this move. We were motivated to identify ways to improve developer satisfaction through architectural improvements. What is the problem we are trying to solve? Therefore, in 2022, we prioritised creating a great developer experience through improvements to our developers’ machine architecture. During early testing performed last year, we ran the same builds on different machines and found that switching to Apple silicon for development could reduce iOS build times by 20% to 30% (and up to 50% with the new M1 Pro and M1 Max chips). One such obstacle was longer build times. What motivated us to perform this research?Īt Spotify, we conduct quarterly Engineering Satisfaction surveys to identify obstacles that diminish developers’ overall satisfaction and productivity. Our survey showed that >90% of surveyed team members gave a rating of 5 (out of 5) for productivity perception and development experience. We sent out a feedback survey to the developers who upgraded their laptops.We worked with Tech Procurement to ensure an early hardware upgrade for client developers, outside of the normal upgrade cycle, for a better client developer experience.Build times on Apple silicon machines were 43% faster than Intel-based Mac ® systems, overall, and up to 50% faster for Android builds and 40% faster for iOS builds.Our analyses found using Apple ® silicon machines to be empirically faster and financially beneficial.We set out to improve build times through multiple changes, one of which was testing out different hardware for our build systems.Developer productivity and satisfaction were compromised due to longer build times, as per our Engineering Satisfaction survey results.We conducted research among 318 engineers and learned that: In line with this, we wanted to improve the coding experience for our development teams through infrastructure changes. TL DR The core motivation for Spotify’s Client Platform (CliP) team is empowering and unblocking client developers and giving teams the tools they need to ensure a happy and satisfying developer experience (DX). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |