Highlight importance of batching index requests#6968
Conversation
Updating the billing dimensions documentation to add information on ingest VCU scaling and strategies for reducing costs by recommending `_bulk` requests. Fixes [#1307](elastic/docs-content-internal#1307)
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
🔍 Preview links for changed docs |
shainaraskas
left a comment
shainaraskas
left a comment
There was a problem hiding this comment.
copy looks real nice. one suggestion to make this bullet fit better with its neighbors.
side note: this bulleted list is getting to be so big that it's hard to scan. we might consider breaking this into subheadings with an intro list.
| * **Machine learning trained model autoscaling**: [Trained model autoscaling](/deploy-manage/autoscaling/trained-model-autoscaling.md) is always enabled and cannot be disabled, ensuring efficient resource usage, reduced costs, and optimal performance without manual configuration. | ||
|
|
||
| Trained model deployments automatically scale down to zero allocations after 24 hours without any inference requests. When they scale up again, they remain active for 5 minutes before they can scale down. During these cooldown periods, you will continue to be billed for the active resources. | ||
| * **Ingest VCU scaling**: Ingest VCU consumption scales with your indexing load. After 15 minutes with no ingest activity, ingest capacity scales down to zero and ingest charges are minimal during idle periods. Continuous indexing requests prevent idle windows, so ingest VCUs remain provisioned and you continue to incur costs. |
There was a problem hiding this comment.
I think maybe we should reframe this using the lever as the title "batch indexing" or similar ... this also feels like it might be part of the "indexing strategies" section
if you break these into subheadings, you could put these two things underneath so people know that both the shape of their data and their indexing rate/strategy matter
alternatively, "indexing strategies" could get a better title like "index size / structure" (not with a slash, but you get it)
2 participants
Summary
Updating the billing dimensions documentation to add information on ingest VCU scaling and strategies for reducing costs by recommending batching requests with the
_bulkoperation.Fixes #1307
Preview available here
Generative AI disclosure