OSSForks/pytorch
1
0
Fork 0
mirror of https://github.com/zebrajr/pytorch.git synced 2025-12-07 12:21:27 +01:00
Code Issues Actions 38 Packages Projects Releases Wiki Activity
0d3d84d866
pytorch/benchmarks/dynamo/pr_time_benchmarks
History
Laith Sakka cc09d3a5ba remove float args benchmark (#155674) 
This benchmark very sensitive. removing it for now until we make it better .

<img width="755" alt="Screenshot 2025-06-11 at 12 01 25 AM" src="https://github.com/user-attachments/assets/01a45ae5-2028-42a2-b819-c30d4db3b5d4" />

Pull Request resolved: https://github.com/pytorch/pytorch/pull/155674
Approved by: https://github.com/bdhirsh, https://github.com/bobrenjc93
2025-06-11 20:34:58 +00:00
..
benchmarks [dynamo] keep C++ symbolic shape guards disabled for benchmarks (#151225) 2025-05-29 23:29:39 +00:00
test_check_result Several enhancements for check_results.py (#137925) 2024-10-26 16:27:55 +00:00
__init__.py
benchmark_runner.sh [inductor] Minor compile time optimizations in DefaultHandler (#146282) 2025-02-08 18:00:40 +00:00
check_results.py refresh expected results (#150166) 2025-05-13 04:04:42 +00:00
expected_results.csv remove float args benchmark (#155674) 2025-06-11 20:34:58 +00:00
log_benchmarking_time.py Only keep ListOfLinears module in basic_modules_benchmarks and add gpu version. (#135730) 2024-09-14 16:45:52 +00:00
README.md add README.md for compile time benchmarks (#143145) 2024-12-13 05:12:26 +00:00

README.md

Instructions on how to make a new compile time benchmark

  1. Make a new benchmark file in /benchmarks/dynamo/pr_time_benchmarks/benchmarks/ eg. 0b75b7ff2b/benchmarks/dynamo/pr_time_benchmarks/benchmarks/add_loop.py
  2. cd into the pr_time_benchmarks directory cd benchmarks/dynamo/pr_time_benchmarks
  3. Run PYTHONPATH=./ python benchmarks/[YOUR_BENCHMARK].py a.txt
  4. (Optional) flip a flag that you know will change the benchmark and run again with b.txt PYTHONPATH=./ python benchmarks/[YOUR_BENCHMARK].py a.txt
  5. Compare a.txt and b.txt located within the benchmarks/dynamo/pr_time_benchmarks folder to make sure things look as you expect
  6. Check in your new benchmark file and submit a new PR
  7. In a few days, if your benchmark is stable, bug Laith Sakka to enable running your benchmark on all PRs. If your a meta employee, you can find the dashboard here: internalfb.com/intern/unidash/dashboard/pt2_diff_time_metrics