Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move AutoTuner into its own Git repository #2833

Open
jeffng-or opened this issue Feb 12, 2025 · 0 comments
Open

Move AutoTuner into its own Git repository #2833

jeffng-or opened this issue Feb 12, 2025 · 0 comments
Assignees
Labels
autotuner Flow autotuner

Comments

@jeffng-or
Copy link
Contributor

Description

The current AutoTuner is loosely coupled with ORFS in that it’s built on top of ORFS, but doesn’t link directly to ORFS. Since it calls ORFS via a shell command, ORFS is really no different than any other tool.

Since we have discussed opportunities for the AutoTuner to call other tools (e.g. bazel-orfs, other third party tools), it makes natural sense to decouple it from ORFS. ORFS will remain the tool-of-choice, of course.

A new set of AutoTuner-specific CI pipelines will need to be created (e.g. smoke tests, regression tests, including QoR, lint/formatting checks, pre-commit hooks)

We might want to couple an ORFS version with an AutoTuner version, but there are other ways of accomplishing the same goal

Suggested Solution

No response

Additional Context

No response

@jeffng-or jeffng-or added the autotuner Flow autotuner label Feb 12, 2025
@vvbandeira vvbandeira self-assigned this Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autotuner Flow autotuner
Projects
None yet
Development

No branches or pull requests

2 participants