Reinstate AA test ElasticSearch 6.7 #3135
Merged
Conversation
This file contains 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
Rosa-Fox
force-pushed
the
aa-test-es-six-seven-user-scope
branch
from
2b1a364
to
dde5947
Compare
We recently ran an AA test for the Search team (#3053). We are going to run it again, hence reinstating it in this PR! The purpose of the A/A test is to test the % of allocation of traffic/sample population based on the current version of elastic (6.7) against itself. A (ES 6.7) vs A (ES6.7). The A/A is solely to identify how the approach allocates traffic. This will provide benchmark data to aid analysis in future AA tests. This time around, the code will stay the same. We will use the same custom dimension and the variant split will still be 50/50. The only difference is that the custom dimension has been scoped as ‘user' as opposed to ‘session’ like it was last time. Scoping the custom dimension has already been done by a performance analyst. We plan to deploy this on Thursday 17 August for 1 week.
Rosa-Fox
force-pushed
the
aa-test-es-six-seven-user-scope
branch
from
dde5947
to
e2c29a9
Compare
Rosa-Fox
added a commit
that referenced
this pull request
Sep 4, 2023
There is currently an AA test running with a 50/50 split [1]. We now want to run a throttled version with a 0.5% split. The C variant has therefore been added to the corresponding govuk-cdn-config PR to soak up the traffic not in A or B. This PR allows the C variant. Z will remain as the control variant. [1]#3135
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Trello
We recently ran an AA test for the Search team.
We are going to run it again, hence reinstating it in this PR!
The purpose of the A/A test is to test the % of allocation of traffic/sample population based on the current version of elastic (6.7) against itself. A (ES 6.7) vs A (ES6.7). The A/A is solely to identify how the approach allocates traffic. This will provide benchmark data to aid analysis in future AA tests.
This time around, the code will stay the same. We will use the same custom dimension and the variant split will still be 50/50. The only difference is that the custom dimension has been scoped as ‘user' as opposed to ‘session’ like it was last time. Scoping the custom dimension has already been done by a performance analyst.
We plan to deploy this on Thursday 17 August for 1 week.
Corresponding CDN config PR
Follow these steps if you are doing a Rails upgrade.