Skip to content

[ML] Explain serverless pricing #741

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.

Sign up for GitHub

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

Closed
wants to merge 2 commits into from
Closed

[ML] Explain serverless pricing #741

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a76c53e
[ML] Explain serverless pricing
prwhelan Mar 11, 2025
3c12fa9
is -> are
prwhelan Mar 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions serverless/pages/ml-nlp-auto-scale.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,9 @@ The used resources for trained model deployments depend on three factors:
* the use case you optimize the model deployment for (ingest or search)
* whether model autoscaling is enabled with adaptive allocations/resources to have dynamic resources, or disabled for static resources

VCUs for ML are based on the amount of vCPU and Memory consumed. For ML, `1` VCU equals `0.125` of vCPU and `1GB` of memory, where vCPUs are measured by allocations multiplied by threads, and where memory is the amount consumed by trained models or ML jobs.
As a math formula, `VCUs = 8 * allocations * threads`, or `1` VCU for every `1GB` of memory consumed, whichever is greater.

The following tables show you the number of allocations, threads, and VCUs available on Serverless when adaptive resources are enabled or disabled.

[discrete]
Expand Down
Loading