Hi @comaniac , subgraph executor get renamed into pipeline executor, and the PR
now only include pipeline executor and schedule logic, could you help for a
review?
---
[Visit
Topic](https://discuss.tvm.apache.org/t/rfc-compute-graph-pipeline-with-new-subgraph-executor/9839/7)
to respond.
Here are my two cents before diving into the detail code review.
1. At the first glance most implementations, including the Relay passes, were
done in Python. It would be better to implement them in C++ for better
performance.
2. The term and namespace "subgraph" is improper and confusing.
3.
@tqchen @comaniac @areusch @tmoreau89 @zhiics @giuseros.
---
[Visit
Topic](https://discuss.tvm.apache.org/t/rfc-compute-graph-pipeline-with-new-subgraph-executor/9839/2)
to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
he
Thanks @comaniac @zhiics @giuseros @JaydeepIMG @JakeStevens for the review and
discussion.
The compute pipeline runtime/executor PR already get
submitted(https://github.com/apache/tvm/pull/7892) , I also propose a new
RFC(https://discuss.tvm.apache.org/t/rfc-compute-graph-pipeline-with-new-s
>This is a follow up RFC for
>https://discuss.tvm.apache.org/t/compute-graph-pipeline/8957
>PR https://github.com/apache/tvm/pull/7892
# **Split relay graph into Subgraph then doing Subgraph Pipeline :RFC**
In this RFC, we present a new framework for subgraph pipelining that first
split rela