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

[Issue]: Can multiple model instances be called concurrently to construct a graph? #949

Closed
2 tasks
c0derm4n opened this issue Aug 16, 2024 · 1 comment
Closed
2 tasks
Labels
community_support Issue handled by community members

Comments

@c0derm4n
Copy link

Is there an existing issue for this?

  • I have searched the existing issues
  • I have checked #657 to validate if my issue is covered by community support

Describe the issue

The speed of constructing graphs is too slow now, especially when using larger local models

Steps to reproduce

No response

GraphRAG Config Used

# Paste your config here

Logs and screenshots

No response

Additional Information

  • GraphRAG Version:
  • Operating System:
  • Python Version:
  • Related Issues:
@c0derm4n c0derm4n added the triage Default label assignment, indicates new issue needs reviewed by a maintainer label Aug 16, 2024
@natoverse
Copy link
Collaborator

We have a number of settings in GraphRAG to tune parallelization and token consumption, but they assume you are working with a single API endpoint. You can add llm config blocks to any step and pass in new config which may help, but more generally I think you're looking for a load-balancing system that spreads requests across multiple endpoints within a single verb. We don't plan to support this specifically because it is more of an infrastructure concern. I would suggest the use of a proxy or gateway that can do this without GraphRAG needing to be aware.

@natoverse natoverse closed this as not planned Won't fix, can't repro, duplicate, stale Aug 16, 2024
@natoverse natoverse added community_support Issue handled by community members and removed triage Default label assignment, indicates new issue needs reviewed by a maintainer labels Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community_support Issue handled by community members
Projects
None yet
Development

No branches or pull requests

2 participants