Update serverless pricing info (#201)

Co-authored-by: George Wallace <[email protected]> Co-authored-by: Liam Thompson <[email protected]> Co-authored-by: florent-leborgne <[email protected]>
elastic · Nov 20, 2024 · b18be69 · b18be69
1 parent 3f7eba7
commit b18be69
Show file tree

Hide file tree

Showing 4 changed files with 44 additions and 46 deletions.
diff --git a/serverless/pages/ingest-your-data.asciidoc b/serverless/pages/ingest-your-data.asciidoc
@@ -24,6 +24,8 @@ This data can be updated, but the value of the content remains relatively consta
 Use connector clients to sync data from a range of popular data sources to {es}.
 You can also send data directly to {es} from your application using the API.
 
+[discrete]
+[[elasticsearch-ingest-time-series-data]]
 **Times series (timestamped) data**
 
 Time series, or timestamped data, describes data that changes frequently and "flows" over time, such as stock quotes, system metrics, and network traffic data.

diff --git a/serverless/pages/manage-billing-monitor-usage.asciidoc b/serverless/pages/manage-billing-monitor-usage.asciidoc
@@ -6,23 +6,19 @@
 
 preview:[]
 
-To find more details about your account usage:
+To get more details about your account usage:
 
 . Navigate to https://cloud.elastic.co/[cloud.elastic.co] and log in to your {ecloud} account.
-. Go to the user icon on the header bar and select **Billing**.
+. In the header bar, click the user icon, then select **Billing**.
 
-On the **Usage** page you can:
+On the **Usage** tab of the **Billing** page, you can:
 
-* Monitor the usage for the current month, including total hourly rate and month-to-date usage
+* Monitor usage for the current month, including month-to-date usage
 * Check the usage breakdown for a selected time range
+* View usage totals by product
 
 [IMPORTANT]
 ====
 The usage breakdown information is an estimate. To get the exact amount you owe for a given month, check your invoices in the <<general-billing-history,billing history>>.
 ====
 
-.{es} minimum runtime VCUs
-[IMPORTANT]
-====
-When you create an {es-serverless} project, a minimum number of VCUs are always allocated to your project to maintain basic ingest and search capabilities. These VCUs incur a minimum cost even with no active usage. Learn more about https://www.elastic.co/pricing/serverless-search#what-are-the-minimum-compute-resource-vcus-on-elasticsearch-serverless[minimum VCUs on {es-serverless}].
-====
diff --git a/serverless/pages/manage-your-project.asciidoc b/serverless/pages/manage-your-project.asciidoc
@@ -34,17 +34,20 @@ The total volume of search-ready data is the sum of the following:
 
 Each project type offers different settings that let you adjust the performance and volume of search-ready data, as well as the features available in your projects.
 
+[discrete]
+[[elasticsearch-manage-project-search-power-settings]]
 |===
 | Setting | Description | Available in
 
 | **Search Power**
-a| Search Power affects search speed by controlling the number of VCUs (Virtual Compute Units) allocated to search-ready data in the project. Additional VCUs provide more compute resources and result in performance gains.
+a| Search Power controls the speed of searches against your data. With Search Power, you can improve search performance by adding more resources for querying, or you can reduce provisioned resources to cut costs.
+Choose from three Search Power settings:
 
-The **Cost-efficient** Search Power setting limits the available cache size, and generates cost savings by reducing search performance.
+**On-demand:** Autoscales based on data and search load, with a lower minimum baseline for resource use. This flexibility results in more variable query latency and reduced maximum throughput.
 
-The **Balanced** Search Power setting ensures that there is sufficient cache for all search-ready data, in order to respond quickly to queries.
+**Performant:** Delivers consistently low latency and autoscales to accommodate moderately high query throughput.
 
-The **Performance** Search Power setting provides more computing resources in addition to the searchable data cache, in order to respond quickly to higher query volumes and more complex queries.
+**High-throughput:** Optimized for high-throughput scenarios, autoscaling to maintain query latency even at very high query volumes.
 | {es-badge}
 
 | **Search Boost Window**

diff --git a/serverless/pages/pricing.asciidoc b/serverless/pages/pricing.asciidoc
@@ -6,51 +6,48 @@
 
 preview:[]
 
-{es} is priced based on the consumption of the underlying
-infrastructure used to support your use case, with the performance
-characteristics you need. We measure by Virtual Compute Units (VCUs), which is a
-slice of RAM, CPU and local disk for caching. The number of VCUs required will
-depend on the amount and the rate of data sent to {es} and retained,
-and the number of searches and latency you require for searches. In addition, if
-you required {ml} for inference or NLP tasks, those VCUs are also
-metered and billed.
+Elasticsearch is priced based on consumption of the underlying
+infrastructure that supports your use case, with the performance
+characteristics you need. Measurements are in Virtual Compute Units (VCUs).
+Each VCU represents a fraction of RAM, CPU, and local disk for caching.
 
-include::../partials/minimum-vcus-detail.asciidoc[]
+The number of VCUs you need is determined by:
+
+* Volume and ingestion rate of your data
+* Data retention requirements 
+* Search query volume
+* Search Power setting
+* Machine learning usage
 
 [discrete]
 [[elasticsearch-billing-information-about-the-vcu-types-search-ingest-and-ml]]
-== Information about the VCU types (Search, Ingest, and ML)
+== VCU types: Search, Indexing, and ML
 
-There are three VCU types in {es}:
+Elasticsearch uses three VCU types:
 
-* **Indexing** — The VCUs used to index the incoming documents to be
-stored in {es}.
-* **Search** — The VCUs used to return search results with the latency and
-Queries per Second (QPS) you require.
-* **Machine Learning** — The VCUs used to perform inference, NLP tasks, and other ML activities.
+* **Indexing:** The VCUs used to index incoming documents.
+* **Search:** The VCUs used to return search results, with the latency and
+queries per second (QPS) you require.
+* **Machine learning:** The VCUs used to perform inference, NLP tasks, and other ML activities.
 
 [discrete]
 [[elasticsearch-billing-information-about-the-search-ai-lake-dimension-gb]]
-== Information about the Search AI Lake dimension (GB)
+== Data storage and billing
+
 
-For {es}, the Search AI Lake is where data is stored and retained. This is
-charged in GBs for the size of data at rest. Depending on the enrichment,
-vectorization and other activities during ingest, this size may be different
-from the original size of the source data.
+{es-serverless} projects store data in the <<elasticsearch-manage-project-search-ai-lake-settings,Search AI Lake>>. You are charged per GB of stored data at rest. Note that if you perform operations at ingest such as vectorization or enrichment, the size of your stored data will differ from the size of the original source data.
 
 [discrete]
 [[elasticsearch-billing-managing-elasticsearch-costs]]
 == Managing {es} costs
 
-You can control costs in a number of ways. Firstly there is the amount of
-data that is retained. {es} will ensure that the most recent data is
-cached, allowing for fast retrieval. Reducing the amount of data means fewer
-Search VCUs may be required. If you need lower latency, then more Search VCUs
-can be added by adjusting the Search Power. A further refinement is for data streams that can be used to store
-time series data. For that type of data, you can further define the number of
-days of data you want cacheable, which will affect the number of Search VCUs and
-therefore the cost. Note that {es-serverless} maintains and bills for
-https://www.elastic.co/pricing/serverless-search#what-are-the-minimum-compute-resource-vcus-on-elasticsearch-serverless[minimum compute resource Ingest and Search VCUs].
-
-For detailed {es-serverless} project rates, check the
-https://www.elastic.co/pricing/serverless-search[{es-serverless} pricing page].
+You can control costs by using a lower Search Power setting or reducing the amount 
+of retained data. 
+
+* **Search Power setting:** <<elasticsearch-manage-project-search-power-settings,Search Power>> controls the speed of searches against your data. With Search Power, you can 
+improve search performance by adding more resources for querying, or you can reduce provisioned 
+resources to cut costs.
+* **Time series data retention:** By limiting the number of days of <<elasticsearch-ingest-time-series-data,time series data>> that are available for caching, 
+you can reduce the number of search VCUs required. 
+
+For detailed {es-serverless} project rates, see the https://www.elastic.co/pricing/serverless-search[{es-serverless} pricing page].