frozenleaves/pytorch
1
0
Fork 0
mirror of https://github.com/pytorch/pytorch.git synced 2025-10-20 21:14:14 +08:00
Code Issues Packages Projects Releases Wiki Activity

Updated PyTorch OSS benchmark infra (markdown)

Huy Do
2025-06-16 13:04:01 -07:00
parent 2bdee303fe
commit 3087ae6260
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
PyTorch-OSS-benchmark-infra.md

@ -76,7 +76,9 @@ Note that the JSON list is optional. Writing JSON record one per line ([JSONEach
### Upload API
The quickest way to upload the benchmark results is to use the [upload_benchmark_results.py](https://github.com/pytorch/pytorch-integration-testing/blob/main/.github/scripts/upload_benchmark_results.py) script. The script requires an `UPLOADER_[USERNAME|PASSWORD]` credential at the moment, so please reach out to PyTorch Dev Infra if you need to use it. For example,
The quickest way to upload the benchmark results is to use the [upload_benchmark_results.py](https://github.com/pytorch/pytorch-integration-testing/blob/main/.github/scripts/upload_benchmark_results.py) script. The script requires an `UPLOADER_[USERNAME|PASSWORD]` credential at the moment, so please reach out to PyTorch Dev Infra if you need to use it. Once written to the database, the benchmark results could be considered immutable because it's a complicated and expensive process to update or delete them.
Here is an example usage:
```
export UPLOADER_USERNAME=<REDACT>
@ -94,6 +96,7 @@ pip install -r requirements.txt
# --repo is where the repo is checkout and built
# --benchmark-name is an unique string that is used to identify the benchmark
# --benchmark-results is where the JSON benchmark result files are kept
# --dry-run is to prepare everything except writing the results to S3
python upload_benchmark_results.py \
--repo pytorch \
--benchmark-name "My PyTorch benchmark" \