[MetaSchedule] Add an API to dump a pruned database#14783
Merged
spectrometerHBH merged 1 commit intoapache:mainfrom May 7, 2023
Merged
[MetaSchedule] Add an API to dump a pruned database#14783spectrometerHBH merged 1 commit intoapache:mainfrom
spectrometerHBH merged 1 commit intoapache:mainfrom
Conversation
Collaborator
|
Thanks for contributing to TVM! Please refer to the contributing guidelines https://tvm.apache.org/docs/contribute/ for useful information and tips. Please request code reviews from Reviewers by @-ing them in a comment.
Generated by tvm-bot |
This was referenced May 6, 2023
This PR introduces the `Database.dump_pruned` API, which makes possible to keep the only optimal record for the workload on disk for easy re-distribution of a MetaSchedule database.
b2c54d9 to
c25483c
Compare
Member
Author
spectrometerHBH
approved these changes
May 7, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces the
Database.dump_prunedAPI, which makes possible to keep the only optimal record for the workload on disk for easy re-distribution of a MetaSchedule database.