[WIP] Fix batched silhouette score reduction aliasing - #2422
Conversation
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
/ok to test f8c9939 |
f8c9939 to
6ec7aeb
Compare
|
/ok to test 6ec7aeb |
|
/ok to test 6ec7aeb |
6ec7aeb to
d24aff2
Compare
|
/ok to test d24aff2 |
d24aff2 to
77aaa23
Compare
|
/ok to test 77aaa23 |
|
The negative-control run behaved as expected. With the presumed fix reverted, This confirms that the stress test detects the unfixed behavior in the target environment. The next step is to restore the fix and rerun the same matrix; the A100/CUDA 12.2 test should then pass. The separate NN-descent recall failure on L4 appears unrelated. |
77aaa23 to
20bd669
Compare
Stores the row-wise minimum for batched silhouette scores in a separate device vector, preventing the reduction output from overwriting matrix elements that may still be read.
Validation
Validates the fix with the temporary
BATCHED_SILHOUETTE_CONCURRENCY_TESTadded inef922834, originallye20bfffcbefore the rebase. The test has since been reverted.As a negative control, reverting the fix while retaining the test caused the A100/CUDA 12.2 CI job to fail: 12 of 512 worker seeds produced 22 batched/non-batched mismatches above the
1e-4tolerance. This confirms that the stress test detects the unfixed reduction-aliasing behavior in the target environment.