Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: use larger disks to avoid throttling #186

Merged
merged 2 commits into from
Oct 28, 2024
Merged

Conversation

lenaschoenburg
Copy link
Member

As we saw in camunda/camunda#21758, a 32 GiB disk is slightly too small for our default workload.

As we saw in camunda/camunda#21758, a 32 GiB disk is slightly too small for our default workload.
@lenaschoenburg
Copy link
Member Author

@Zelldon Ping on this one. Let me know if you disagree.

@ChrisKujawa
Copy link
Member

Currently unsure whether we should increase the disk size as it increases cost (not much i guess but still).

I'm currently investigating whether we can move our benchmarks to a different process model/load, which might not suffer of this.

@ChrisKujawa ChrisKujawa requested a review from npepinpe October 28, 2024 17:40
Copy link
Member

@npepinpe npepinpe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have more budget now since we dropped the whole CI runners 👍

I'd rather we reduce work by throwing money at it, and correct afterwards (we do keep track of usage).

@ChrisKujawa ChrisKujawa merged commit aff06d4 into main Oct 28, 2024
4 checks passed
@lenaschoenburg lenaschoenburg deleted the ls/increase-disk-size branch October 29, 2024 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants