Debug process time

At some point last week, our build went from 15m to 2h 22m. Jenkins only keeps track of our last 10 builds and we are past that now so I can’t do a full compare, but I did have a chance to compare the fast build to the first slow build briefly and the gem versions were the same and the only code change for that build was a text change on one page.

Running with --verbose on jenkins shows most pages taking 13-17s to process

11:50:15 == Request: /api/rest/client-libraries/ruby/latest/PureCloud/OutOfOffice.html
11:50:15 == Finishing Request: api/rest/client-libraries/ruby/latest/PureCloud/OutOfOffice.html (13.99s)
11:50:15 create localBuild/api/rest/client-libraries/ruby/latest/PureCloud/OutOfOffice.html

but locally it goes much quicker

== Request: /api/rest/client-libraries/ruby/latest/PureCloud/OutOfOffice.html
== Finishing Request: api/rest/client-libraries/ruby/latest/PureCloud/OutOfOffice.html (3.62s)
create localBuild/api/rest/client-libraries/ruby/latest/PureCloud/OutOfOffice.html

Are there any other ways I can debug what is going on during those additional 10s to see if it is something that I’m doing? Our build servers are pretty beefy and things are slow even when there isn’t anything else building on the server.

there is a --profile flag that can be used with build, that generates a ruby-perf report in profile/build.html. For me, looks like the bulk of time is spent doing file io