Skip to content

GODRIVER-3638 Prohibit using failpoints on sharded topologies. #2168

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

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

matthewdale
Copy link
Collaborator

GODRIVER-3638

Summary

Background & Motivation

@matthewdale matthewdale force-pushed the godriver3638-prohibit-failpoint branch from 3ab7bb9 to 9aa3b5a Compare August 12, 2025 23:38
Copy link
Contributor

API Change Report

No changes found!

Copy link
Contributor

🧪 Performance Results

Commit SHA: 9aa3b5a

The following benchmark tests for version 689bd07c58efd400073436e2 had statistically significant changes (i.e., |z-score| > 1.96):

Benchmark Measurement % Change Patch Value Stable Region H-Score Z-Score
BenchmarkMultiFindMany ops_per_second_min -87.2389 4490.9104 Avg: 35192.1334
Med: 37049.3868
Stdev: 15106.5931
0.7213 -2.0323
BenchmarkMultiFindMany total_mem_allocs 26.3555 461355.0000 Avg: 365124.5000
Med: 364944.5000
Stdev: 12416.6057
0.9384 7.7501
BenchmarkMultiFindMany total_bytes_allocated 26.3442 750082112.0000 Avg: 593681280.0000
Med: 593390168.0000
Stdev: 19635635.7607
0.9401 7.9652
BenchmarkMultiFindMany total_time_seconds 16.2900 1.2170 Avg: 1.0465
Med: 1.0288
Stdev: 0.0780
0.8287 2.1847
BenchmarkSingleFindOneByID allocs_per_op 0.3904 360.0000 Avg: 358.6000
Med: 359.0000
Stdev: 0.5982
0.7893 2.3402

For a comprehensive view of all microbenchmark results for this PR's commit, please check out the Evergreen perf task for this patch.

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.

1 participant