-
Notifications
You must be signed in to change notification settings - Fork 25.3k
Fix memory usage estimation for ELSER models #131630
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
Fix memory usage estimation for ELSER models #131630
Conversation
Pinging @elastic/ml-core (Team:ML) |
Hi @jan-elastic, I've created a changelog YAML for you. |
@@ -96,7 +99,7 @@ boolean hasEverBeenAllocated() { | |||
|
|||
public long estimateMemoryUsageBytes(int allocations) { | |||
return StartTrainedModelDeploymentAction.estimateMemoryUsageBytes( | |||
deploymentId, | |||
modelId, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are the important changes: passing the model ID instead of the deployment ID to the memory estimator.
If the deployment ID is passed, the method isElserV1Or2Model doesn't work, because it's passed .elser-2-elasticsearch
or my-elser
, which doesn't start with .elser_model_2
.
38afae6
to
874149d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM Good catch
* Pass model ID instead of deployment ID to memory estimator * Update docs/changelog/131630.yaml
💔 Backport failed
You can use sqren/backport to manually backport by running |
* Pass model ID instead of deployment ID to memory estimator * Update docs/changelog/131630.yaml
No description provided.