Looking at the resource usage for the build checks job, the CPU seems like it could be tuned down, and while RAM does at one point spike between 1/3 to just below 1/2 usage of 16 GB on XLarge, the job itself seems to set a Node limit of roughly 4GB, far below the 8GB which is on a Large resource class. So thought it would be wise to try to see if we can tune this down for improved resource usage.
Same seems to apply to nightly, so made that change too.
Seems like it worked? Pegs CPU for a short bit, but the duration was no longer than normal (in fact, this run happened to be slightly shorter at 11mins than others I've seen).
Description:
Looking at the resource usage for the build checks job, the CPU seems like it could be tuned down, and while RAM does at one point spike between 1/3 to just below 1/2 usage of 16 GB on XLarge, the job itself seems to set a Node limit of roughly 4GB, far below the 8GB which is on a Large resource class. So thought it would be wise to try to see if we can tune this down for improved resource usage.
Same seems to apply to nightly, so made that change too.
Sample run from a recent mainline build:
https://app.circleci.com/pipelines/github/okta/okta-developer-docs/3586/workflows/23e11945-8f10-4cb5-bb2b-cc49f254eb81/jobs/7256/steps
Resolves: