Some comments after reading the example and the current PR. * The APIs are still confusing to me. I agree with the `job` part but not others. `config_library` still doesn't look like a "library". It's more like a job manager according to your proposal. The use case `config_library.tune()` is also weird, because we already use `tuner.tune` for each task. In my personal opinion, something like `job_manager.session()` would be more reasonable.
* I didn't see the features you claimed neither in the PR or the example. Specifically, how to control if I want to record all configs or just the best one? how to resume a job? I don't think the current PR will skip any well-tuned job when resuming. I would suggest making that example more concrete and realistic first before the implementation so that we can all refer to it. I also think it's fine to create a separate tutorial for this feature. In summary, here are the points I wish to see in the tutorial: * How to create a config library and what's the controllable options. * How a config library resumes a job. * How to specify the log file mode (all or the best). * How to apply the log file generated by the config library to the rest building process. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/dmlc/tvm/issues/4150#issuecomment-547252660
