At the moment, the only way to A/B test different values of relevancyStrictness is to create a second Virtual Replica (VR). While A/B tests can be run on a single index to compare different query parameters, those parameters usually apply to primary (ie. non-virtual) indices.
Since relevancyStrictness is specific to VRs, testing it will require a separate replica. We understand that managing an additional replica may not always be ideal but:
- Virtual Replicas do not increase your record count usage.
- They automatically stay in sync with your primary index - any add, update, or delete operations applied to the primary will also be applied to both the replicas, so they will stay in sync.