Hello David, Is the full build: * CPU bound * Memory bound * IOPS bound ?
Which can be found using top/iostat metrics during its run. If the later, then I guess that a good test would be to run the build on an EBS volume of GP3 type (minimum 3000 IOPS, up to 16000 IOPS) and see if that improves significantly build time ; but of course the more IOPS, the higher price is. Another approach to keep price/performance ratio as low as possible could be to use cheap AWS instances with https://plugins.jenkins.io/ec2-fleet/ to let Jenkins create AWS instances based on load. Disclaimer: I haven't experienced the later approach myself, but I work in a place with a homemade build system, designed to allocate build jobs on a kind of grid of large VMs, with quota management & automatic cleanups to keep costs within planned bounds. Alex Le mer. 12 oct. 2022 à 00:05, David Blevins <david.blev...@gmail.com> a écrit : > > All, > > I'm collecting some stats on how long it takes to run our full build exactly > as Jenkins does. The goal is to work with them to see if we can get some > better hardware -- I assume that will require donations, etc. > > If you'd like to help in collecting data, here's the script I'm running: > > - curl > https://gist.githubusercontent.com/dblevins/b39cc3300bcdd89b426ca33b87b5452b/raw/7c68d4df71e9246c8bf2d0a741f8b145ca5d0820/buildtime.sh > | bash > > Send the time reported in the build.log along with your system information > (os, number of cores, if you disk is an SSD, etc) > > > -- > David Blevins > http://twitter.com/dblevins > http://www.tomitribe.com >
