@tqchen Thanks for the comment and sharing of thoughts. Yes, the fundamental problem here is the serialization of code and weights. Code is relatively easy to handle and weights are the real problem. I agree that a json runtime introduces another layer of abstraction for graph which the current CSourceMdoule way doesn't. I think I don't fully understand the layered approach you proposed here.
Could you please elaborate a bit more about the execution flow after introducing it? and also when should we build and cache the engine, i.e. what's the input for the process to build the engine? Thanks. --- [Visit Topic](https://discuss.tvm.ai/t/byoc-runtime-json-runtime-for-byoc/6579/6) 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/fa96b487cf8824ee39b58f26a00789b93aeee2d12ce9ec736c965a71f5eb4ebc).
