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

[Option] Add debug_cache_tuning option #120

Merged
merged 3 commits into from Feb 20, 2023

Conversation

yaoyaoding
Copy link
Member

Previously, hidet will keep all the kernels that generated during tuning process, which makes the cache directory grow very fast (e.g., several GiB).

In this PR, we by default do not keep those kernels. If needed (for the debug purpose), one could keep those kernels via

hidet.option.debug_cache_tuning()

@yaoyaoding yaoyaoding merged commit f9383f1 into hidet-org:main Feb 20, 2023
@yaoyaoding yaoyaoding deleted the cache-tuning-option branch February 20, 2023 20:44
KTong821 pushed a commit to KTong821/hidet that referenced this pull request Apr 24, 2024
With https://github.com/CentML/hidet/pull/69 there will be a lot more
C++ code introduced into the runtime, I think it's a good idea to have
some standardization. For now this is just doing formatting (no linting,
which takes more work to set up + has more opinions about right vs.
wrong).

Summary of changes:
- Update `format.sh` to support formatting just Python, C++, or both
- Add `clang-format` to the existing lint/format workflow
- Apply `clang-format` changes to existing code; I've set up the
configuration to try to minimize the number of changes and have excluded
the float16/bfloat16 code

Example workflow failure @ 4cc430c:
<img width="1155" alt="image"
src="https://github.com/CentML/hidet/assets/43303581/9566e9dd-bd01-4638-b556-11afaf7e6e52">
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.

None yet

1 participant