Feat/add-vertexai-location #210
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@danny-avila is there any updates on this (rather small) improvement? It's a bit critical for usage in EU and regulated environments. I am looking forward to this change gets merged :-) |
|
@danny-avila do you have an outlook when you will be able to take a look at this PR? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem: We identified unexpected costs originating from the US region in our billing reports for the RAG system deployed exclusively in europe-west3.
Root Cause: Upon investigation, we determined that the Google text-embedding models always default to the us-central1 location, causing cross-regional data processing charges.
Solution: To enforce regional alignment and eliminate unnecessary costs, we have implemented an environment variable. This allows us to explicitly configure the model's location, ensuring all operations remain within the europe-west3 region.
Bonus: We also upgraded the model from 004 to the latest version 005