Add second SP3 dedicated host#296
Merged
Merged
Conversation
markcor
approved these changes
May 21, 2026
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
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.
Summary
Context
Follow-up to #295, which added the first dedicated host for the SP3 perf experiment.
Based on https://mozilla-hub.atlassian.net/browse/RELOPS-2375 for the Bug 2039391 Windows 11 25H2 GPU Speedometer 3 dedicated-host experiment. The existing fxci-config template spec targets the host group, so adding another host in the same group should allow Azure automatic placement to use the added capacity.
Validation
Terraform plan/apply will be run separately after the StandardNVADSA10v5Family quota bump is available.