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

Support for Multiple LiteLLM Models #35

Closed
bhumika-scogo opened this issue Jul 29, 2024 · 3 comments
Closed

Support for Multiple LiteLLM Models #35

bhumika-scogo opened this issue Jul 29, 2024 · 3 comments

Comments

@bhumika-scogo
Copy link

bhumika-scogo commented Jul 29, 2024

Great job with the current routing setup!
I’m wondering if there’s a possibility to expand the routing capabilities to include multiple LiteLLM models. Currently, it seems we can only route between one strong and one weak model.

Here’s why it would be beneficial for example:

  • Microsoft-PHI: Useful for enterprise tasks and Microsoft integrations.

  • Google-Gemma: Great for tasks that involve Google’s ecosystem.

  • Meta-Llama3: Ideal for open-source and research-based queries.

  • Azure-GPT: Perfect for projects , troubleshooting services, or offering guidance on optimizing cloud infrastructure .

  • Currently as we have, for high-quality responses on complex queries, a strong model like OpenAI GPT.

Supporting these models would help optimize costs and improve how we handle various data types and queries. Is there a way to integrate this with RouteLLM? Any advice or guidance would be greatly appreciated, let me know by when it will be published.

@iojw
Copy link
Collaborator

iojw commented Aug 3, 2024

Hi there, thank you for your interest! The multi-model routing problem is definitely interesting, and more research is required to support this use-case. We would be excited to support any efforts or contributions in this space.

@bitnom
Copy link
Contributor

bitnom commented Aug 6, 2024

duplicate of #23

@iojw
Copy link
Collaborator

iojw commented Aug 11, 2024

Yes, we'll track progress for this in #23.

@iojw iojw closed this as completed Aug 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants