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

first commit #205

Merged
merged 8 commits into from
Sep 13, 2023
Merged

first commit #205

merged 8 commits into from
Sep 13, 2023

Conversation

izzbizz
Copy link
Collaborator

@izzbizz izzbizz commented Sep 13, 2023

No description provided.

@izzbizz izzbizz self-assigned this Sep 13, 2023
@vercel
Copy link

vercel bot commented Sep 13, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
haystack-home ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 13, 2023 11:47am

content/blog/rag-deployment/index.md Outdated Show resolved Hide resolved
While the nitty-gritty technical details of scaling are handled by Kubernetes, we have the ability to tweak it based on the type of pipeline. To do this, it’s useful to think about the following questions:



Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And 1 question: What's the role of model deployment services here? Does it make sense to mention them? E.g.: If I go with Sagemaker, will sagemaker handle scaling model requests? That incurs a cost but maybe it's worth it?
@izzbizz @ArzelaAscoIi

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. We might want to be a bit careful with not create confusion for the reader, but what do you think about adding a comment about: "Considering an additional model hosting services like sagemaker (or hf inference) might be helpful to spearately scale model inference"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not 100% sure about the wording

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about:
The nitty-gritty technical details of scaling are handled by our orchestration tool. Additionally, model hosting services like SageMaker or Hugging Face Inference can be helpful to scale model inference separately. Aside from these automated solutions, we have the ability to tweak the scaling of our pipelines ourselves.

While the nitty-gritty technical details of scaling are handled by Kubernetes, we have the ability to tweak it based on the type of pipeline. To do this, it’s useful to think about the following questions:



Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. We might want to be a bit careful with not create confusion for the reader, but what do you think about adding a comment about: "Considering an additional model hosting services like sagemaker (or hf inference) might be helpful to spearately scale model inference"

While the nitty-gritty technical details of scaling are handled by Kubernetes, we have the ability to tweak it based on the type of pipeline. To do this, it’s useful to think about the following questions:



Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not 100% sure about the wording

@TuanaCelik TuanaCelik merged commit 674c149 into main Sep 13, 2023
2 checks passed
@TuanaCelik TuanaCelik deleted the rag-deployment branch September 13, 2023 11:53
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

Successfully merging this pull request may close these issues.

None yet

3 participants