## Difference between the logs for Ansor and AutoTVM
There are two major differences between ansor's log and autotvm's log 1. The workload for Ansor is a subgraph defined by multiple `tvm.compute`, while the workload for autotvm is a single operator. To index log quickly, Ansor stores a hash value of the subgraph as the workload key. 2. Ansor saves the whole serialized schedule as `config` (in json format), while autotvm only stores the parameters. However, Ansor's new log format can still fit into the @tqchen 's design of top-level fields. ## Other thoughts 1. The current log file is an append-able text file, where one line corresponds to one log item. I can edit it with a text editor. If we use a binary format, I want this property to be preserved. 2. If we make the log longer and more readable, there will be a lot of redundancy in the file. For example, for a single tuning job, the same long target string will appear in all lines. Do we have methods to compress it? --- [Visit Topic](https://discuss.tvm.ai/t/rfc-canonicalizing-autotvm-log-format/7038/19) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/c1321c86b5ca1091ad5aa7c44918ac2e0ba75eace798d6ee38994a124243d2e4).
