50% time increase in 1x steps running tests in parallel

[Martin Defeche]

Hello,

Since the rollout of the cloud runtime 2, we noticed a 50% time increase when running python tests in parallel on a 1x step (~15min to ~23min).

We identified the runtime based on the log at the end of the first step:

Cloud runtime: 1 # before
Cloud runtime: 2 # now

It was clearly stated that there won't be a decrease in compute for 1x steps

Important: We want to emphasise that this is NOT a reduction in compute for 1x steps. In fact, 2x steps will see a significant INCREASE in compute allocation. The move to a dedicated CPU model means each visible CPU will provide more actual compute power.

Is there something to tweak to get the same results as before ?

We were already impacted by the decision to restrict the `atlassian-ip-ranges` to 4x/8x steps which forced us to move certain steps to more expensive sizes.

With those two problems, our build minutes usage has significantly increased, and our bill too.

Are there plans to mitigate the price increase for customers caused by this migration ?

Thank you

[Swetha Boyapati]

HI Martin, 

Good day!!I'm Swetha from Bitbucket Cloud Support. 

We have created a support ticket for this issue as we need to look into the builds which would need us accessing the repo. You'll get an email notification with the support ticket details. 

Cheers, 
Swetha Boyapati