New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding a readiness matrix of the various first party Backends #6912
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: zeryx <1892175+zeryx@users.noreply.github.com>
@zeryx - a table of supported backends is a great idea. we are in the process of updating our docs to be able to pull in information from the backends into the generated html. as well. As it stands we'll have to review more and be thoughtful in the designations of quality and recommendation. Since we don't have documented standards (yet) - I'd want to hold off on merging something like this in order to avoid giving a false impression. I would first like us to document what recommended / alpha / ready / etc. mean |
Migrated OpenVINO to "Beta" Signed-off-by: zeryx <1892175+zeryx@users.noreply.github.com>
hey @nnshah1 that's great to hear. And fully agreed on what we should be declaring ready or recommended - I've updated to only contain "recommended" and "ready" for now. Let me know if you'd like to chat more about it! |
…ilities matrix. Signed-off-by: zeryx <1892175+zeryx@users.noreply.github.com>
…hub markdown) Signed-off-by: zeryx <1892175+zeryx@users.noreply.github.com>
Signed-off-by: zeryx <1892175+zeryx@users.noreply.github.com>
This PR adds a support matrix of the various first-party Triton backends, and indicates which are the "recommended path" for new developers looking to explore Triton.
The table also links to the backends themselves, along with an end-to-end example showcasing how to "get started" with that backend.