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

Feat/use jumpstart streamlined for new llm options #192

Merged
merged 16 commits into from
Dec 19, 2024

Conversation

aidanrussell
Copy link

@aidanrussell aidanrussell commented Dec 19, 2024

Using Sagemaker Jumpstart containers and model weights stored in an AWS account in the eu-west-2 region, we redeploy the existing two small LLMs. This process then trivially allows for new LLMs to be added. Note that through jumpstart we also optimize the instance size and ensure the correct environment variables for the model, which can otherwise be difficult. It should be possible to also store these containers and model weights in our own account, I need to check how to do that, but I do wonder if it adds value since this way it never goes to the public internet in any case as it stays within the AWS region.

@aidanrussell aidanrussell requested a review from a team as a code owner December 19, 2024 12:42
@aidanrussell aidanrussell changed the base branch from main to feat/sagemaker-llms December 19, 2024 12:42
@aidanrussell aidanrussell merged commit e8aa255 into feat/sagemaker-llms Dec 19, 2024
1 check passed
@aidanrussell aidanrussell deleted the feat/new_llm_options branch December 19, 2024 19:23
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.

1 participant