Using runners with less RAM where possible #33127
Merged
+15
−11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
category: CI
akladiev
approved these changes
Dec 5, 2025
Merged
via the queue into
openvinotoolkit:master
with commit Dec 8, 2025
e4b55ef
190 of 192 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Details:
Tests on
aks-linux-8-cores-64gbself-hosted runners don't consume that much memory, metrics and my tests (#32993) show it. Switching them to 32 GB RAM runners to optimize costs.Windows Debug builds are also not limited by the amount of RAM, unlike Windows Conditional Compilation builds). In my measurements the duration increase was negligible (within 2 minutes), so switching them to lower RAM runner version as well.
CC_Build job in Windows Conditional Compilation workflow runs perfectly fine on standard Windows build runner (aks-win-16-cores-32gb-build), although it takes 5 minutes longer, it's not a big deal, because CPU Functional Tests job runs in parallel with it and takes around 40 minutes.