Skip to content

[inductor] Make experimental benchmarker parameters configurable via env vars#3223

Open
tomjen12 wants to merge 1 commit into
release/2.11from
configurable-experimental-benchmarker
Open

[inductor] Make experimental benchmarker parameters configurable via env vars#3223
tomjen12 wants to merge 1 commit into
release/2.11from
configurable-experimental-benchmarker

Conversation

@tomjen12
Copy link
Copy Markdown

💡 Summary

The experimental benchmarker currently hardcodes parameters like estimation_iters and memory_warmup_iters. This PR makes them configurable via environment variables to allow easier tuning for different hardware and workloads without modifying source code.
Added environment variables:

  • TORCHINDUCTOR_EXPERIMENTAL_BENCHMARKER_ESTIMATION_ITERS (default: 5)
  • TORCHINDUCTOR_EXPERIMENTAL_BENCHMARKER_MEMORY_WARMUP_ITERS (default: 100)
  • TORCHINDUCTOR_EXPERIMENTAL_BENCHMARKER_BENCHMARK_ITERS (default: 100)
  • TORCHINDUCTOR_EXPERIMENTAL_BENCHMARKER_MAX_DURATION (default: 25)

Added environment variables to configure `estimation_iters`, `memory_warmup_iters`, `benchmark_iters`, and `max_benchmark_duration` for the experimental benchmarker.

This allows users to tune the benchmarking process without modifying the source code, while preserving the original default values and respecting explicitly passed arguments.
@tomjen12 tomjen12 requested a review from jataylo May 14, 2026 02:57
@rocm-repo-management-api
Copy link
Copy Markdown

rocm-repo-management-api Bot commented May 14, 2026

Jenkins build for 2d745a70d0b5ee8c8b40ba0e7a0249d4fc97a465 commit finished as FAILURE
Links: Pipeline Overview / Build artifacts / Test Results

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