apache / tvm

Open deep learning compiler stack for cpu, gpu and specialized accelerators

Home Page:https://tvm.apache.org/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Features Discussion before Next Release v0.16.0

ysh329 opened this issue · comments

Hi all, based on our quarterly release schedule, next release is coming on April. The next release is the first version based on Unity branch.
As is known to all, the Unity branch owns our all features about LLM. The next release is vital for downstream companies, especially depended on TVM, whatever software or hardware companies.

Enable those software or hardware companies to have ability using large language model. Advance the democratization of AI.

Thus, it's necessary to discuss required features:

  • These features will be the highlight of the release, attracting downstream companies or users to switch to this new version.
  • Besides, bugs should be considered, especially those obstacle new and core features.

I hope we can list required highlight features and bugs needed to be fixed before release schedule begin.

On the TVM unity side, we can say

  • First support of relax, with dynamic shape and pipeline
  • dlight module for optimizing LLM TIR workloads on GPU
  • disco module for initial SPMD multi-GPU support

On the TVM unity side, we can say

  • First support of relax, with dynamic shape and pipeline
  • dlight module for optimizing LLM TIR workloads on GPU
  • disco module for initial SPMD multi-GPU support

Great! These points can be highlighted.

I'm thinking whether having any other PRs (about** big feature and bug issues**), which have not been merged or not beed fixed yet but required by other users or downstream companies.

Hope these users can propose these features or bug issues in advance before release schedue begins. Because, these required items maybe merge or cherry-picked during release, or delay release.

Currently, I found two bugs may need more attention:

  • Bug about CI: It seems that there are still a few test cases that need to be fixed to ensure that our CI can be fully functional, so that downstream companies or users can use it more safely:
    1. #16633.
  • Bug about RPC: RPC as a core function has always been there, this bug may impact user's debug etc.
    1. #16707.

Thus, I hope these issues above can be fixed.


Hope anyone can proposal other required feature or issues as soon as possible before release.

Closed without obstacling release v0.16.0.