crosscheck
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| crosscheck [2023/09/11 10:33] – [Errors Found (updated on 2023.09.07)] mino | crosscheck [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== A preliminary cross-check done already ====== | ||
| - | Computing resources available in clouds are diverse in their performance, | ||
| - | |||
| - | * Every time a new instance created a benchmark program which counts a small subset was executed and the time and the result was recorded. If the answer was wrong, that resource was never used. I actually saw a few such resources and it is noteworthy that some versions of docker environment with multiple RTX-4090s produced wrong answers due to a failure of inter-GPU atomic transactions. I avoided multiple 4090s working together and used them separately instead. | ||
| - | * As a postmortem verification, | ||
| - | | ||
| - | ==== The full cross-check in progress ==== | ||
| - | |||
| - | If every subtotal is calculated twice and the two results match, the counts should be considered correct (provided the code is correct). The re-counting is in progress and is done up to 8% as of 2023/09/05. | ||
| - | |||
| - | ==== Errors Found (updated on 2023.09.07) ==== | ||
| - | |||
| - | During the thorough double-check, | ||
| - | |||
| - | Correcting these errors increased the number by 960(40x24). | ||
| - | |||
| - | While these errors have not damaged my confidence in the logic and the code I used, it is possible that errors of similar nature may still be contained in the result. Therefore, the results should be considered unconfirmed until the thorough double-check will be completed. | ||
| - | |||
| - | |||
crosscheck.1694395987.txt.gz · Last modified: 2023/09/11 10:33 by mino
