Skip to content
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

multi model graphs request propagation #4260

Closed
saeid93 opened this issue Aug 5, 2022 · 2 comments
Closed

multi model graphs request propagation #4260

saeid93 opened this issue Aug 5, 2022 · 2 comments
Labels
Projects

Comments

@saeid93
Copy link
Contributor

saeid93 commented Aug 5, 2022

Follow up to Slack channel question with @adriangonz . As part of a project, I have a set of interconnected nodes (each node is a Triton server) in which each of them has a number of models (with the same goal) and I want each request to pass through a different set of models. For example, I want request 1 to pass through model 1 in node 1 -> model 1 in node 2 -> model 1 in node 3, and another path R2. The path for each request is determined prior to run the request and can be possibly sent through metadata to the Triton servers and Seldon core graph.

181790732-dcbab48e-2658-426c-a409-a7fdf5a119e9 (2)

P.S A possible use case is that I have requests with different latency-accuracy requirements and I want to choose the path of the request based on that.

@ukclivecox
Copy link
Contributor

In general you could achieve this by

  1. Extending your graph to have a Router before each item. Although this is a challenge with Triton as that is using the V2 protocol.
  2. Utilize Triton's business logic scripting to call the models as needed

In general we will be investigating these use cases in v2 of our APIs.

@ukclivecox ukclivecox added this to Needs triage in V2 APIs via automation Aug 15, 2022
@ukclivecox ukclivecox added the v2 label Aug 15, 2022
@ukclivecox
Copy link
Contributor

Please test in v2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
V2 APIs
Needs triage
Development

No branches or pull requests

2 participants