> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tensor9.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Memorystore for Redis costs
> Compare Memorystore for Redis backend choices using explicit service-adapter planning assumptions.
Tensor9 BYOC planning comparisons for `google::1.0.0::memorystore::redis`, with backend choices shown together. Read [how to think about service-adapter costs](/byoc/service-adapters/debugging/costs/overview) for price scope and capacity qualification, or return to [additional services](/byoc/service-adapters/debugging/costs/additional-services).
## Google Memorystore Redis allocated cache capacity → Azure Managed Redis
Origin API: `google::1.0.0::memorystore::redis`. Target backend: `azure::1.0.0::cache::redis`.
**Planning estimate with editable assumptions.** Unit rates, workload amplification and capacity assumptions are educated guesses awaiting verification. The displayed amounts are planning estimates, not verified provider list-price quotes or benchmark-qualified capacity. Region names identify the authored scenario assumptions.
**Designed mapping.** This cost model describes an intended adapter. Its estimated price does not establish a delivered or selectable backend.
### Google Memorystore Redis allocated cache capacity · Redis key reads per second
**Planning estimate with editable assumptions.** These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available.
Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.
Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Only discrete samples are shown. Unpriced means no target quote or cost difference is available within the sizing policy.
| Redis key reads per second (operations/s) | Origin | Target scenario | Target | Difference |
| -: | -: | - | -: | -: |
| 0 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 0 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 100 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 100 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 1000 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 1000 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 10000 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 10000 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 100000 | 160.6 | Planning allocation · one copy | 1728.64 | 1568.04 |
| 100000 | 160.6 | Planning allocation · two copies | 3457.28 | 3296.68 |
| 1000000 | 160.6 | Planning allocation · one copy | Unpriced | Unavailable |
| 1000000 | 160.6 | Planning allocation · two copies | Unpriced | Unavailable |
**Estimated allocation from planning assumptions; not benchmark calibrated.**
The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.
| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 operations/s / Planning allocation · one copy | PlanningAssumption | 10 / 20 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 0 operations/s / Planning allocation · two copies | PlanningAssumption | 10 / 20 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100 operations/s / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100 operations/s / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1000 operations/s / Planning allocation · one copy | PlanningAssumption | 1010 / 2020 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1000 operations/s / Planning allocation · two copies | PlanningAssumption | 1010 / 2020 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 10000 operations/s / Planning allocation · one copy | PlanningAssumption | 10010 / 20020 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 10000 operations/s / Planning allocation · two copies | PlanningAssumption | 10010 / 20020 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100000 operations/s / Planning allocation · one copy | PlanningAssumption | 100010 / 200020 | 29 | 32 | 128 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100000 operations/s / Planning allocation · two copies | PlanningAssumption | 100010 / 200020 | 29 | 32 | 128 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1000000 operations/s / Planning allocation · one copy | Unpriced | 1000010 / 2000020 | 286 | Unpriced | Unpriced | Unpriced | 6 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 1000000 operations/s / Planning allocation · two copies | Unpriced | 1000010 / 2000020 | 286 | Unpriced | Unpriced | Unpriced | 6 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
**Curve assumptions**
| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Planning allocation · one copy | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · one copy | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · one copy | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · one copy | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · one copy | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · one copy | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · one copy | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · one copy | Target CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · one copy | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · one copy | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · one copy | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · one copy | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · one copy | Target price guess · read | 0 | USD/read |
| Planning allocation · one copy | Target price guess · write | 0 | USD/write |
| Planning allocation · one copy | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · one copy | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · one copy | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · one copy | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · one copy | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · one copy | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · one copy | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · one copy | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · one copy | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · one copy | Target price guess · input token | 0 | USD/input token |
| Planning allocation · one copy | Target price guess · output token | 0 | USD/output token |
| Planning allocation · one copy | Approximate target service minimum | 0 | USD/month |
| Planning allocation · one copy | Minimum primary CPU | 2 | vCPU |
| Planning allocation · one copy | Minimum primary RAM | 8 | GiB |
| Planning allocation · one copy | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · one copy | Additional full-price standby copy | 0 | 0 or 1 |
| Planning allocation · one copy | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · one copy | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · one copy | Planning peak / mean work | 2 | multiplier |
| Planning allocation · one copy | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · one copy | Planning disk utilization | 0.7 | fraction |
| Planning allocation · one copy | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · one copy | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · one copy | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · one copy | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink write price guess | 0.000005 | USD/write |
| Planning allocation · two copies | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · two copies | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · two copies | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · two copies | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · two copies | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · two copies | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · two copies | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · two copies | Target CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · two copies | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · two copies | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · two copies | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · two copies | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · two copies | Target price guess · read | 0 | USD/read |
| Planning allocation · two copies | Target price guess · write | 0 | USD/write |
| Planning allocation · two copies | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · two copies | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · two copies | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · two copies | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · two copies | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · two copies | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · two copies | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · two copies | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · two copies | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · two copies | Target price guess · input token | 0 | USD/input token |
| Planning allocation · two copies | Target price guess · output token | 0 | USD/output token |
| Planning allocation · two copies | Approximate target service minimum | 0 | USD/month |
| Planning allocation · two copies | Minimum primary CPU | 2 | vCPU |
| Planning allocation · two copies | Minimum primary RAM | 8 | GiB |
| Planning allocation · two copies | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · two copies | Additional full-price standby copy | 1 | 0 or 1 |
| Planning allocation · two copies | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · two copies | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · two copies | Planning peak / mean work | 2 | multiplier |
| Planning allocation · two copies | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · two copies | Planning disk utilization | 0.7 | fraction |
| Planning allocation · two copies | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · two copies | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · two copies | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · two copies | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink write price guess | 0.000005 | USD/write |
* Only the selected native meter varies; other usage quantities and assumptions retain their displayed defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
* Unit prices and capacity coefficients are editable authored planning guesses, not verified provider tariffs or measured capacity.
* The origin is the exact registered google::1.0.0::memorystore::redis identity. Renamed products and future aliases require explicit mapping updates.
* Source allocated CPU-hours and memory-hours establish independent minimum target allocation. Neither management API requests nor a key-operation count is an instance count.
* Peak weighted key-operation work and resident data can promote the allocation above those minima. CPU rounds to whole cores and RAM to quarter GiB.
* CPU and RAM are aggregate resources over 730 hours. Selected backend tariffs own replica count, availability configuration and actual instance shapes.
* A multi-core estimate assumes the workload can be partitioned. Redis command execution, hot keys, cross-key transactions and clustering can prevent linear scale.
* Zero allocated resources and zero workload do not prove target scale-to-zero; the selected backend may retain a provisioned minimum.
* All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
* Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification.
* Cache storedGiB represents resident RAM footprint, not billable SSD. Persistence, snapshots and backup disks require a separate explicit allocation.
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.
Excluded costs and workload features:
* Replication traffic, snapshots, persistence write IOPS, network egress, cluster management premiums, licenses and migration.
* Command-specific complexity, Lua/scripts, module behavior, eviction/expiry churn, blocking commands, multi-key locality and benchmark-qualified latency.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.
Planning assumptions authored: 2026-10-18. Model: `plan-b08274a0e3c1951367529e035513fd97297ddf56` / `2026-10-18.planning.1`. Curve: `workload-1`.
### Google Memorystore Redis allocated cache capacity · Redis key writes per second
**Planning estimate with editable assumptions.** These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available.
Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.
Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Only discrete samples are shown. Unpriced means no target quote or cost difference is available within the sizing policy.
| Redis key writes per second (operations/s) | Origin | Target scenario | Target | Difference |
| -: | -: | - | -: | -: |
| 0 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 0 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 100 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 100 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 1000 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 1000 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 10000 | 160.6 | Planning allocation · one copy | 432.16 | 271.56 |
| 10000 | 160.6 | Planning allocation · two copies | 864.32 | 703.72 |
| 100000 | 160.6 | Planning allocation · one copy | 3457.28 | 3296.68 |
| 100000 | 160.6 | Planning allocation · two copies | 6914.56 | 6753.96 |
| 1000000 | 160.6 | Planning allocation · one copy | Unpriced | Unavailable |
| 1000000 | 160.6 | Planning allocation · two copies | Unpriced | Unavailable |
**Estimated allocation from planning assumptions; not benchmark calibrated.**
The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.
| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 operations/s / Planning allocation · one copy | PlanningAssumption | 100 / 200 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 0 operations/s / Planning allocation · two copies | PlanningAssumption | 100 / 200 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100 operations/s / Planning allocation · one copy | PlanningAssumption | 200 / 400 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100 operations/s / Planning allocation · two copies | PlanningAssumption | 200 / 400 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1000 operations/s / Planning allocation · one copy | PlanningAssumption | 1100 / 2200 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1000 operations/s / Planning allocation · two copies | PlanningAssumption | 1100 / 2200 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 10000 operations/s / Planning allocation · one copy | PlanningAssumption | 10100 / 20200 | 6 | 8 | 32 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 10000 operations/s / Planning allocation · two copies | PlanningAssumption | 10100 / 20200 | 6 | 8 | 32 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100000 operations/s / Planning allocation · one copy | PlanningAssumption | 100100 / 200200 | 58 | 64 | 256 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100000 operations/s / Planning allocation · two copies | PlanningAssumption | 100100 / 200200 | 58 | 64 | 256 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1000000 operations/s / Planning allocation · one copy | Unpriced | 1000100 / 2000200 | 572 | Unpriced | Unpriced | Unpriced | 6 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 1000000 operations/s / Planning allocation · two copies | Unpriced | 1000100 / 2000200 | 572 | Unpriced | Unpriced | Unpriced | 6 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
**Curve assumptions**
| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Planning allocation · one copy | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · one copy | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · one copy | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · one copy | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · one copy | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · one copy | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · one copy | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · one copy | Target CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · one copy | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · one copy | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · one copy | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · one copy | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · one copy | Target price guess · read | 0 | USD/read |
| Planning allocation · one copy | Target price guess · write | 0 | USD/write |
| Planning allocation · one copy | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · one copy | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · one copy | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · one copy | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · one copy | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · one copy | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · one copy | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · one copy | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · one copy | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · one copy | Target price guess · input token | 0 | USD/input token |
| Planning allocation · one copy | Target price guess · output token | 0 | USD/output token |
| Planning allocation · one copy | Approximate target service minimum | 0 | USD/month |
| Planning allocation · one copy | Minimum primary CPU | 2 | vCPU |
| Planning allocation · one copy | Minimum primary RAM | 8 | GiB |
| Planning allocation · one copy | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · one copy | Additional full-price standby copy | 0 | 0 or 1 |
| Planning allocation · one copy | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · one copy | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · one copy | Planning peak / mean work | 2 | multiplier |
| Planning allocation · one copy | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · one copy | Planning disk utilization | 0.7 | fraction |
| Planning allocation · one copy | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · one copy | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · one copy | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · one copy | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink write price guess | 0.000005 | USD/write |
| Planning allocation · two copies | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · two copies | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · two copies | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · two copies | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · two copies | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · two copies | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · two copies | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · two copies | Target CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · two copies | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · two copies | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · two copies | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · two copies | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · two copies | Target price guess · read | 0 | USD/read |
| Planning allocation · two copies | Target price guess · write | 0 | USD/write |
| Planning allocation · two copies | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · two copies | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · two copies | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · two copies | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · two copies | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · two copies | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · two copies | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · two copies | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · two copies | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · two copies | Target price guess · input token | 0 | USD/input token |
| Planning allocation · two copies | Target price guess · output token | 0 | USD/output token |
| Planning allocation · two copies | Approximate target service minimum | 0 | USD/month |
| Planning allocation · two copies | Minimum primary CPU | 2 | vCPU |
| Planning allocation · two copies | Minimum primary RAM | 8 | GiB |
| Planning allocation · two copies | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · two copies | Additional full-price standby copy | 1 | 0 or 1 |
| Planning allocation · two copies | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · two copies | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · two copies | Planning peak / mean work | 2 | multiplier |
| Planning allocation · two copies | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · two copies | Planning disk utilization | 0.7 | fraction |
| Planning allocation · two copies | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · two copies | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · two copies | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · two copies | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink write price guess | 0.000005 | USD/write |
* Only the selected native meter varies; other usage quantities and assumptions retain their displayed defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
* Unit prices and capacity coefficients are editable authored planning guesses, not verified provider tariffs or measured capacity.
* The origin is the exact registered google::1.0.0::memorystore::redis identity. Renamed products and future aliases require explicit mapping updates.
* Source allocated CPU-hours and memory-hours establish independent minimum target allocation. Neither management API requests nor a key-operation count is an instance count.
* Peak weighted key-operation work and resident data can promote the allocation above those minima. CPU rounds to whole cores and RAM to quarter GiB.
* CPU and RAM are aggregate resources over 730 hours. Selected backend tariffs own replica count, availability configuration and actual instance shapes.
* A multi-core estimate assumes the workload can be partitioned. Redis command execution, hot keys, cross-key transactions and clustering can prevent linear scale.
* Zero allocated resources and zero workload do not prove target scale-to-zero; the selected backend may retain a provisioned minimum.
* All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
* Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification.
* Cache storedGiB represents resident RAM footprint, not billable SSD. Persistence, snapshots and backup disks require a separate explicit allocation.
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.
Excluded costs and workload features:
* Replication traffic, snapshots, persistence write IOPS, network egress, cluster management premiums, licenses and migration.
* Command-specific complexity, Lua/scripts, module behavior, eviction/expiry churn, blocking commands, multi-key locality and benchmark-qualified latency.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.
Planning assumptions authored: 2026-10-18. Model: `plan-b08274a0e3c1951367529e035513fd97297ddf56` / `2026-10-18.planning.1`. Curve: `workload-2`.
### Google Memorystore Redis allocated cache capacity · Resident logical cache data
**Planning estimate with editable assumptions.** These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available.
Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.
Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Only discrete samples are shown. Unpriced means no target quote or cost difference is available within the sizing policy.
| Resident logical cache data (GiB-month) | Origin | Target scenario | Target | Difference |
| -: | -: | - | -: | -: |
| 0 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 0 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 1 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 1 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 10 | 160.6 | Planning allocation · one copy | 240.17 | 79.57 |
| 10 | 160.6 | Planning allocation · two copies | 480.34 | 319.74 |
| 100 | 160.6 | Planning allocation · one copy | 3457.28 | 3296.68 |
| 100 | 160.6 | Planning allocation · two copies | 6914.56 | 6753.96 |
| 1000 | 160.6 | Planning allocation · one copy | Unpriced | Unavailable |
| 1000 | 160.6 | Planning allocation · two copies | Unpriced | Unavailable |
| 10000 | 160.6 | Planning allocation · one copy | Unpriced | Unavailable |
| 10000 | 160.6 | Planning allocation · two copies | Unpriced | Unavailable |
**Estimated allocation from planning assumptions; not benchmark calibrated.**
The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.
| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 GiB-month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 0 | `service-adapter-planning-2026-10-18.1` | None reported |
| 0 GiB-month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 0 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1 GiB-month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 1.5 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1 GiB-month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 1.5 | `service-adapter-planning-2026-10-18.1` | None reported |
| 10 GiB-month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 3 | 4 | 21.5 | 0 | 15 | `service-adapter-planning-2026-10-18.1` | None reported |
| 10 GiB-month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 3 | 4 | 21.5 | 0 | 15 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100 GiB-month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 27 | 64 | 256 | 0 | 150 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100 GiB-month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 27 | 64 | 256 | 0 | 150 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1000 GiB-month / Planning allocation · one copy | Unpriced | 110 / 220 | 268 | Unpriced | Unpriced | Unpriced | 1500 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 1000 GiB-month / Planning allocation · two copies | Unpriced | 110 / 220 | 268 | Unpriced | Unpriced | Unpriced | 1500 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 10000 GiB-month / Planning allocation · one copy | Unpriced | 110 / 220 | 2679 | Unpriced | Unpriced | Unpriced | 15000 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 10000 GiB-month / Planning allocation · two copies | Unpriced | 110 / 220 | 2679 | Unpriced | Unpriced | Unpriced | 15000 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
**Curve assumptions**
| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Planning allocation · one copy | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · one copy | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · one copy | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · one copy | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · one copy | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · one copy | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · one copy | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · one copy | Target CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · one copy | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · one copy | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · one copy | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · one copy | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · one copy | Target price guess · read | 0 | USD/read |
| Planning allocation · one copy | Target price guess · write | 0 | USD/write |
| Planning allocation · one copy | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · one copy | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · one copy | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · one copy | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · one copy | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · one copy | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · one copy | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · one copy | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · one copy | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · one copy | Target price guess · input token | 0 | USD/input token |
| Planning allocation · one copy | Target price guess · output token | 0 | USD/output token |
| Planning allocation · one copy | Approximate target service minimum | 0 | USD/month |
| Planning allocation · one copy | Minimum primary CPU | 2 | vCPU |
| Planning allocation · one copy | Minimum primary RAM | 8 | GiB |
| Planning allocation · one copy | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · one copy | Additional full-price standby copy | 0 | 0 or 1 |
| Planning allocation · one copy | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · one copy | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · one copy | Planning peak / mean work | 2 | multiplier |
| Planning allocation · one copy | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · one copy | Planning disk utilization | 0.7 | fraction |
| Planning allocation · one copy | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · one copy | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · one copy | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · one copy | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink write price guess | 0.000005 | USD/write |
| Planning allocation · two copies | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · two copies | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · two copies | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · two copies | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · two copies | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · two copies | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · two copies | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · two copies | Target CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · two copies | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · two copies | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · two copies | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · two copies | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · two copies | Target price guess · read | 0 | USD/read |
| Planning allocation · two copies | Target price guess · write | 0 | USD/write |
| Planning allocation · two copies | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · two copies | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · two copies | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · two copies | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · two copies | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · two copies | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · two copies | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · two copies | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · two copies | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · two copies | Target price guess · input token | 0 | USD/input token |
| Planning allocation · two copies | Target price guess · output token | 0 | USD/output token |
| Planning allocation · two copies | Approximate target service minimum | 0 | USD/month |
| Planning allocation · two copies | Minimum primary CPU | 2 | vCPU |
| Planning allocation · two copies | Minimum primary RAM | 8 | GiB |
| Planning allocation · two copies | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · two copies | Additional full-price standby copy | 1 | 0 or 1 |
| Planning allocation · two copies | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · two copies | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · two copies | Planning peak / mean work | 2 | multiplier |
| Planning allocation · two copies | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · two copies | Planning disk utilization | 0.7 | fraction |
| Planning allocation · two copies | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · two copies | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · two copies | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · two copies | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink write price guess | 0.000005 | USD/write |
* Only the selected native meter varies; other usage quantities and assumptions retain their displayed defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
* Unit prices and capacity coefficients are editable authored planning guesses, not verified provider tariffs or measured capacity.
* The origin is the exact registered google::1.0.0::memorystore::redis identity. Renamed products and future aliases require explicit mapping updates.
* Source allocated CPU-hours and memory-hours establish independent minimum target allocation. Neither management API requests nor a key-operation count is an instance count.
* Peak weighted key-operation work and resident data can promote the allocation above those minima. CPU rounds to whole cores and RAM to quarter GiB.
* CPU and RAM are aggregate resources over 730 hours. Selected backend tariffs own replica count, availability configuration and actual instance shapes.
* A multi-core estimate assumes the workload can be partitioned. Redis command execution, hot keys, cross-key transactions and clustering can prevent linear scale.
* Zero allocated resources and zero workload do not prove target scale-to-zero; the selected backend may retain a provisioned minimum.
* All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
* Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification.
* Cache storedGiB represents resident RAM footprint, not billable SSD. Persistence, snapshots and backup disks require a separate explicit allocation.
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.
Excluded costs and workload features:
* Replication traffic, snapshots, persistence write IOPS, network egress, cluster management premiums, licenses and migration.
* Command-specific complexity, Lua/scripts, module behavior, eviction/expiry churn, blocking commands, multi-key locality and benchmark-qualified latency.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.
Planning assumptions authored: 2026-10-18. Model: `plan-b08274a0e3c1951367529e035513fd97297ddf56` / `2026-10-18.planning.1`. Curve: `workload-3`.
### Google Memorystore Redis allocated cache capacity · Allocated source cache CPU-hours
**Planning estimate with editable assumptions.** These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available.
Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.
Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Only discrete samples are shown. Unpriced means no target quote or cost difference is available within the sizing policy.
| Allocated source cache CPU-hours (vCPU-hour/month) | Origin | Target scenario | Target | Difference |
| -: | -: | - | -: | -: |
| 0 | 87.6 | Planning allocation · one copy | 113.515 | 25.915 |
| 0 | 87.6 | Planning allocation · two copies | 227.03 | 139.43 |
| 730 | 124.1 | Planning allocation · one copy | 113.515 | -10.585 |
| 730 | 124.1 | Planning allocation · two copies | 227.03 | 102.93 |
| 1460 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 1460 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 5840 | 379.6 | Planning allocation · one copy | 864.32 | 484.72 |
| 5840 | 379.6 | Planning allocation · two copies | 1728.64 | 1349.04 |
| 23360 | 1255.6 | Planning allocation · one copy | 3457.28 | 2201.68 |
| 23360 | 1255.6 | Planning allocation · two copies | 6914.56 | 5658.96 |
| 93440 | 4759.6 | Planning allocation · one copy | Unpriced | Unavailable |
| 93440 | 4759.6 | Planning allocation · two copies | Unpriced | Unavailable |
**Estimated allocation from planning assumptions; not benchmark calibrated.**
The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.
| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 vCPU-hour/month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 2 | 2 | 9.25 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 0 vCPU-hour/month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 2 | 2 | 9.25 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 730 vCPU-hour/month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 2 | 2 | 9.25 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 730 vCPU-hour/month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 2 | 2 | 9.25 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1460 vCPU-hour/month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1460 vCPU-hour/month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 5840 vCPU-hour/month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 10 | 16 | 64 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 5840 vCPU-hour/month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 10 | 16 | 64 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 23360 vCPU-hour/month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 37 | 64 | 256 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 23360 vCPU-hour/month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 37 | 64 | 256 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 93440 vCPU-hour/month / Planning allocation · one copy | Unpriced | 110 / 220 | 148 | Unpriced | Unpriced | Unpriced | 6 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 93440 vCPU-hour/month / Planning allocation · two copies | Unpriced | 110 / 220 | 148 | Unpriced | Unpriced | Unpriced | 6 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
**Curve assumptions**
| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Planning allocation · one copy | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · one copy | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · one copy | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · one copy | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · one copy | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · one copy | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · one copy | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · one copy | Target CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · one copy | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · one copy | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · one copy | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · one copy | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · one copy | Target price guess · read | 0 | USD/read |
| Planning allocation · one copy | Target price guess · write | 0 | USD/write |
| Planning allocation · one copy | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · one copy | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · one copy | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · one copy | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · one copy | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · one copy | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · one copy | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · one copy | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · one copy | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · one copy | Target price guess · input token | 0 | USD/input token |
| Planning allocation · one copy | Target price guess · output token | 0 | USD/output token |
| Planning allocation · one copy | Approximate target service minimum | 0 | USD/month |
| Planning allocation · one copy | Minimum primary CPU | 2 | vCPU |
| Planning allocation · one copy | Minimum primary RAM | 8 | GiB |
| Planning allocation · one copy | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · one copy | Additional full-price standby copy | 0 | 0 or 1 |
| Planning allocation · one copy | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · one copy | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · one copy | Planning peak / mean work | 2 | multiplier |
| Planning allocation · one copy | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · one copy | Planning disk utilization | 0.7 | fraction |
| Planning allocation · one copy | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · one copy | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · one copy | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · one copy | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink write price guess | 0.000005 | USD/write |
| Planning allocation · two copies | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · two copies | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · two copies | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · two copies | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · two copies | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · two copies | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · two copies | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · two copies | Target CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · two copies | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · two copies | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · two copies | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · two copies | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · two copies | Target price guess · read | 0 | USD/read |
| Planning allocation · two copies | Target price guess · write | 0 | USD/write |
| Planning allocation · two copies | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · two copies | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · two copies | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · two copies | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · two copies | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · two copies | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · two copies | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · two copies | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · two copies | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · two copies | Target price guess · input token | 0 | USD/input token |
| Planning allocation · two copies | Target price guess · output token | 0 | USD/output token |
| Planning allocation · two copies | Approximate target service minimum | 0 | USD/month |
| Planning allocation · two copies | Minimum primary CPU | 2 | vCPU |
| Planning allocation · two copies | Minimum primary RAM | 8 | GiB |
| Planning allocation · two copies | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · two copies | Additional full-price standby copy | 1 | 0 or 1 |
| Planning allocation · two copies | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · two copies | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · two copies | Planning peak / mean work | 2 | multiplier |
| Planning allocation · two copies | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · two copies | Planning disk utilization | 0.7 | fraction |
| Planning allocation · two copies | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · two copies | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · two copies | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · two copies | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink write price guess | 0.000005 | USD/write |
* Only the selected native meter varies; other usage quantities and assumptions retain their displayed defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
* Unit prices and capacity coefficients are editable authored planning guesses, not verified provider tariffs or measured capacity.
* The origin is the exact registered google::1.0.0::memorystore::redis identity. Renamed products and future aliases require explicit mapping updates.
* Source allocated CPU-hours and memory-hours establish independent minimum target allocation. Neither management API requests nor a key-operation count is an instance count.
* Peak weighted key-operation work and resident data can promote the allocation above those minima. CPU rounds to whole cores and RAM to quarter GiB.
* CPU and RAM are aggregate resources over 730 hours. Selected backend tariffs own replica count, availability configuration and actual instance shapes.
* A multi-core estimate assumes the workload can be partitioned. Redis command execution, hot keys, cross-key transactions and clustering can prevent linear scale.
* Zero allocated resources and zero workload do not prove target scale-to-zero; the selected backend may retain a provisioned minimum.
* All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
* Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification.
* Cache storedGiB represents resident RAM footprint, not billable SSD. Persistence, snapshots and backup disks require a separate explicit allocation.
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.
Excluded costs and workload features:
* Replication traffic, snapshots, persistence write IOPS, network egress, cluster management premiums, licenses and migration.
* Command-specific complexity, Lua/scripts, module behavior, eviction/expiry churn, blocking commands, multi-key locality and benchmark-qualified latency.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.
Planning assumptions authored: 2026-10-18. Model: `plan-b08274a0e3c1951367529e035513fd97297ddf56` / `2026-10-18.planning.1`. Curve: `workload-4`.
## Google Memorystore Redis allocated cache capacity → ElastiCache
Origin API: `google::1.0.0::memorystore::redis`. Target backend: `aws::1.0.0::elasticache`.
**Planning estimate with editable assumptions.** Unit rates, workload amplification and capacity assumptions are educated guesses awaiting verification. The displayed amounts are planning estimates, not verified provider list-price quotes or benchmark-qualified capacity. Region names identify the authored scenario assumptions.
**Designed mapping.** This cost model describes an intended adapter. Its estimated price does not establish a delivered or selectable backend.
### Google Memorystore Redis allocated cache capacity · Redis key reads per second
**Planning estimate with editable assumptions.** These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available.
Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.
Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Only discrete samples are shown. Unpriced means no target quote or cost difference is available within the sizing policy.
| Redis key reads per second (operations/s) | Origin | Target scenario | Target | Difference |
| -: | -: | - | -: | -: |
| 0 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 0 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 100 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 100 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 1000 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 1000 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 10000 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 10000 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 100000 | 160.6 | Planning allocation · one copy | 1728.64 | 1568.04 |
| 100000 | 160.6 | Planning allocation · two copies | 3457.28 | 3296.68 |
| 1000000 | 160.6 | Planning allocation · one copy | Unpriced | Unavailable |
| 1000000 | 160.6 | Planning allocation · two copies | Unpriced | Unavailable |
**Estimated allocation from planning assumptions; not benchmark calibrated.**
The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.
| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 operations/s / Planning allocation · one copy | PlanningAssumption | 10 / 20 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 0 operations/s / Planning allocation · two copies | PlanningAssumption | 10 / 20 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100 operations/s / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100 operations/s / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1000 operations/s / Planning allocation · one copy | PlanningAssumption | 1010 / 2020 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1000 operations/s / Planning allocation · two copies | PlanningAssumption | 1010 / 2020 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 10000 operations/s / Planning allocation · one copy | PlanningAssumption | 10010 / 20020 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 10000 operations/s / Planning allocation · two copies | PlanningAssumption | 10010 / 20020 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100000 operations/s / Planning allocation · one copy | PlanningAssumption | 100010 / 200020 | 29 | 32 | 128 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100000 operations/s / Planning allocation · two copies | PlanningAssumption | 100010 / 200020 | 29 | 32 | 128 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1000000 operations/s / Planning allocation · one copy | Unpriced | 1000010 / 2000020 | 286 | Unpriced | Unpriced | Unpriced | 6 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 1000000 operations/s / Planning allocation · two copies | Unpriced | 1000010 / 2000020 | 286 | Unpriced | Unpriced | Unpriced | 6 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
**Curve assumptions**
| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Planning allocation · one copy | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · one copy | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · one copy | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · one copy | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · one copy | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · one copy | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · one copy | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · one copy | Target CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · one copy | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · one copy | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · one copy | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · one copy | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · one copy | Target price guess · read | 0 | USD/read |
| Planning allocation · one copy | Target price guess · write | 0 | USD/write |
| Planning allocation · one copy | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · one copy | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · one copy | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · one copy | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · one copy | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · one copy | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · one copy | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · one copy | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · one copy | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · one copy | Target price guess · input token | 0 | USD/input token |
| Planning allocation · one copy | Target price guess · output token | 0 | USD/output token |
| Planning allocation · one copy | Approximate target service minimum | 0 | USD/month |
| Planning allocation · one copy | Minimum primary CPU | 2 | vCPU |
| Planning allocation · one copy | Minimum primary RAM | 8 | GiB |
| Planning allocation · one copy | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · one copy | Additional full-price standby copy | 0 | 0 or 1 |
| Planning allocation · one copy | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · one copy | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · one copy | Planning peak / mean work | 2 | multiplier |
| Planning allocation · one copy | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · one copy | Planning disk utilization | 0.7 | fraction |
| Planning allocation · one copy | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · one copy | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · one copy | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · one copy | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink write price guess | 0.000005 | USD/write |
| Planning allocation · two copies | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · two copies | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · two copies | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · two copies | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · two copies | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · two copies | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · two copies | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · two copies | Target CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · two copies | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · two copies | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · two copies | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · two copies | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · two copies | Target price guess · read | 0 | USD/read |
| Planning allocation · two copies | Target price guess · write | 0 | USD/write |
| Planning allocation · two copies | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · two copies | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · two copies | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · two copies | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · two copies | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · two copies | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · two copies | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · two copies | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · two copies | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · two copies | Target price guess · input token | 0 | USD/input token |
| Planning allocation · two copies | Target price guess · output token | 0 | USD/output token |
| Planning allocation · two copies | Approximate target service minimum | 0 | USD/month |
| Planning allocation · two copies | Minimum primary CPU | 2 | vCPU |
| Planning allocation · two copies | Minimum primary RAM | 8 | GiB |
| Planning allocation · two copies | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · two copies | Additional full-price standby copy | 1 | 0 or 1 |
| Planning allocation · two copies | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · two copies | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · two copies | Planning peak / mean work | 2 | multiplier |
| Planning allocation · two copies | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · two copies | Planning disk utilization | 0.7 | fraction |
| Planning allocation · two copies | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · two copies | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · two copies | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · two copies | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink write price guess | 0.000005 | USD/write |
* Only the selected native meter varies; other usage quantities and assumptions retain their displayed defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
* Unit prices and capacity coefficients are editable authored planning guesses, not verified provider tariffs or measured capacity.
* The origin is the exact registered google::1.0.0::memorystore::redis identity. Renamed products and future aliases require explicit mapping updates.
* Source allocated CPU-hours and memory-hours establish independent minimum target allocation. Neither management API requests nor a key-operation count is an instance count.
* Peak weighted key-operation work and resident data can promote the allocation above those minima. CPU rounds to whole cores and RAM to quarter GiB.
* CPU and RAM are aggregate resources over 730 hours. Selected backend tariffs own replica count, availability configuration and actual instance shapes.
* A multi-core estimate assumes the workload can be partitioned. Redis command execution, hot keys, cross-key transactions and clustering can prevent linear scale.
* Zero allocated resources and zero workload do not prove target scale-to-zero; the selected backend may retain a provisioned minimum.
* All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
* Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification.
* Cache storedGiB represents resident RAM footprint, not billable SSD. Persistence, snapshots and backup disks require a separate explicit allocation.
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.
Excluded costs and workload features:
* Replication traffic, snapshots, persistence write IOPS, network egress, cluster management premiums, licenses and migration.
* Command-specific complexity, Lua/scripts, module behavior, eviction/expiry churn, blocking commands, multi-key locality and benchmark-qualified latency.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.
Planning assumptions authored: 2026-10-18. Model: `plan-a5dd44a392cc5d4a1c85d03f803d3dc9f6e65da4` / `2026-10-18.planning.1`. Curve: `workload-1`.
### Google Memorystore Redis allocated cache capacity · Redis key writes per second
**Planning estimate with editable assumptions.** These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available.
Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.
Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Only discrete samples are shown. Unpriced means no target quote or cost difference is available within the sizing policy.
| Redis key writes per second (operations/s) | Origin | Target scenario | Target | Difference |
| -: | -: | - | -: | -: |
| 0 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 0 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 100 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 100 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 1000 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 1000 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 10000 | 160.6 | Planning allocation · one copy | 432.16 | 271.56 |
| 10000 | 160.6 | Planning allocation · two copies | 864.32 | 703.72 |
| 100000 | 160.6 | Planning allocation · one copy | 3457.28 | 3296.68 |
| 100000 | 160.6 | Planning allocation · two copies | 6914.56 | 6753.96 |
| 1000000 | 160.6 | Planning allocation · one copy | Unpriced | Unavailable |
| 1000000 | 160.6 | Planning allocation · two copies | Unpriced | Unavailable |
**Estimated allocation from planning assumptions; not benchmark calibrated.**
The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.
| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 operations/s / Planning allocation · one copy | PlanningAssumption | 100 / 200 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 0 operations/s / Planning allocation · two copies | PlanningAssumption | 100 / 200 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100 operations/s / Planning allocation · one copy | PlanningAssumption | 200 / 400 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100 operations/s / Planning allocation · two copies | PlanningAssumption | 200 / 400 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1000 operations/s / Planning allocation · one copy | PlanningAssumption | 1100 / 2200 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1000 operations/s / Planning allocation · two copies | PlanningAssumption | 1100 / 2200 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 10000 operations/s / Planning allocation · one copy | PlanningAssumption | 10100 / 20200 | 6 | 8 | 32 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 10000 operations/s / Planning allocation · two copies | PlanningAssumption | 10100 / 20200 | 6 | 8 | 32 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100000 operations/s / Planning allocation · one copy | PlanningAssumption | 100100 / 200200 | 58 | 64 | 256 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100000 operations/s / Planning allocation · two copies | PlanningAssumption | 100100 / 200200 | 58 | 64 | 256 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1000000 operations/s / Planning allocation · one copy | Unpriced | 1000100 / 2000200 | 572 | Unpriced | Unpriced | Unpriced | 6 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 1000000 operations/s / Planning allocation · two copies | Unpriced | 1000100 / 2000200 | 572 | Unpriced | Unpriced | Unpriced | 6 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
**Curve assumptions**
| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Planning allocation · one copy | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · one copy | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · one copy | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · one copy | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · one copy | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · one copy | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · one copy | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · one copy | Target CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · one copy | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · one copy | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · one copy | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · one copy | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · one copy | Target price guess · read | 0 | USD/read |
| Planning allocation · one copy | Target price guess · write | 0 | USD/write |
| Planning allocation · one copy | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · one copy | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · one copy | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · one copy | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · one copy | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · one copy | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · one copy | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · one copy | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · one copy | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · one copy | Target price guess · input token | 0 | USD/input token |
| Planning allocation · one copy | Target price guess · output token | 0 | USD/output token |
| Planning allocation · one copy | Approximate target service minimum | 0 | USD/month |
| Planning allocation · one copy | Minimum primary CPU | 2 | vCPU |
| Planning allocation · one copy | Minimum primary RAM | 8 | GiB |
| Planning allocation · one copy | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · one copy | Additional full-price standby copy | 0 | 0 or 1 |
| Planning allocation · one copy | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · one copy | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · one copy | Planning peak / mean work | 2 | multiplier |
| Planning allocation · one copy | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · one copy | Planning disk utilization | 0.7 | fraction |
| Planning allocation · one copy | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · one copy | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · one copy | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · one copy | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink write price guess | 0.000005 | USD/write |
| Planning allocation · two copies | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · two copies | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · two copies | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · two copies | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · two copies | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · two copies | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · two copies | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · two copies | Target CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · two copies | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · two copies | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · two copies | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · two copies | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · two copies | Target price guess · read | 0 | USD/read |
| Planning allocation · two copies | Target price guess · write | 0 | USD/write |
| Planning allocation · two copies | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · two copies | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · two copies | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · two copies | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · two copies | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · two copies | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · two copies | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · two copies | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · two copies | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · two copies | Target price guess · input token | 0 | USD/input token |
| Planning allocation · two copies | Target price guess · output token | 0 | USD/output token |
| Planning allocation · two copies | Approximate target service minimum | 0 | USD/month |
| Planning allocation · two copies | Minimum primary CPU | 2 | vCPU |
| Planning allocation · two copies | Minimum primary RAM | 8 | GiB |
| Planning allocation · two copies | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · two copies | Additional full-price standby copy | 1 | 0 or 1 |
| Planning allocation · two copies | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · two copies | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · two copies | Planning peak / mean work | 2 | multiplier |
| Planning allocation · two copies | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · two copies | Planning disk utilization | 0.7 | fraction |
| Planning allocation · two copies | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · two copies | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · two copies | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · two copies | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink write price guess | 0.000005 | USD/write |
* Only the selected native meter varies; other usage quantities and assumptions retain their displayed defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
* Unit prices and capacity coefficients are editable authored planning guesses, not verified provider tariffs or measured capacity.
* The origin is the exact registered google::1.0.0::memorystore::redis identity. Renamed products and future aliases require explicit mapping updates.
* Source allocated CPU-hours and memory-hours establish independent minimum target allocation. Neither management API requests nor a key-operation count is an instance count.
* Peak weighted key-operation work and resident data can promote the allocation above those minima. CPU rounds to whole cores and RAM to quarter GiB.
* CPU and RAM are aggregate resources over 730 hours. Selected backend tariffs own replica count, availability configuration and actual instance shapes.
* A multi-core estimate assumes the workload can be partitioned. Redis command execution, hot keys, cross-key transactions and clustering can prevent linear scale.
* Zero allocated resources and zero workload do not prove target scale-to-zero; the selected backend may retain a provisioned minimum.
* All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
* Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification.
* Cache storedGiB represents resident RAM footprint, not billable SSD. Persistence, snapshots and backup disks require a separate explicit allocation.
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.
Excluded costs and workload features:
* Replication traffic, snapshots, persistence write IOPS, network egress, cluster management premiums, licenses and migration.
* Command-specific complexity, Lua/scripts, module behavior, eviction/expiry churn, blocking commands, multi-key locality and benchmark-qualified latency.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.
Planning assumptions authored: 2026-10-18. Model: `plan-a5dd44a392cc5d4a1c85d03f803d3dc9f6e65da4` / `2026-10-18.planning.1`. Curve: `workload-2`.
### Google Memorystore Redis allocated cache capacity · Resident logical cache data
**Planning estimate with editable assumptions.** These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available.
Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.
Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Only discrete samples are shown. Unpriced means no target quote or cost difference is available within the sizing policy.
| Resident logical cache data (GiB-month) | Origin | Target scenario | Target | Difference |
| -: | -: | - | -: | -: |
| 0 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 0 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 1 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 1 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 10 | 160.6 | Planning allocation · one copy | 240.17 | 79.57 |
| 10 | 160.6 | Planning allocation · two copies | 480.34 | 319.74 |
| 100 | 160.6 | Planning allocation · one copy | 3457.28 | 3296.68 |
| 100 | 160.6 | Planning allocation · two copies | 6914.56 | 6753.96 |
| 1000 | 160.6 | Planning allocation · one copy | Unpriced | Unavailable |
| 1000 | 160.6 | Planning allocation · two copies | Unpriced | Unavailable |
| 10000 | 160.6 | Planning allocation · one copy | Unpriced | Unavailable |
| 10000 | 160.6 | Planning allocation · two copies | Unpriced | Unavailable |
**Estimated allocation from planning assumptions; not benchmark calibrated.**
The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.
| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 GiB-month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 0 | `service-adapter-planning-2026-10-18.1` | None reported |
| 0 GiB-month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 0 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1 GiB-month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 1.5 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1 GiB-month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 1.5 | `service-adapter-planning-2026-10-18.1` | None reported |
| 10 GiB-month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 3 | 4 | 21.5 | 0 | 15 | `service-adapter-planning-2026-10-18.1` | None reported |
| 10 GiB-month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 3 | 4 | 21.5 | 0 | 15 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100 GiB-month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 27 | 64 | 256 | 0 | 150 | `service-adapter-planning-2026-10-18.1` | None reported |
| 100 GiB-month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 27 | 64 | 256 | 0 | 150 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1000 GiB-month / Planning allocation · one copy | Unpriced | 110 / 220 | 268 | Unpriced | Unpriced | Unpriced | 1500 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 1000 GiB-month / Planning allocation · two copies | Unpriced | 110 / 220 | 268 | Unpriced | Unpriced | Unpriced | 1500 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 10000 GiB-month / Planning allocation · one copy | Unpriced | 110 / 220 | 2679 | Unpriced | Unpriced | Unpriced | 15000 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 10000 GiB-month / Planning allocation · two copies | Unpriced | 110 / 220 | 2679 | Unpriced | Unpriced | Unpriced | 15000 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
**Curve assumptions**
| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Planning allocation · one copy | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · one copy | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · one copy | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · one copy | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · one copy | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · one copy | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · one copy | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · one copy | Target CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · one copy | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · one copy | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · one copy | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · one copy | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · one copy | Target price guess · read | 0 | USD/read |
| Planning allocation · one copy | Target price guess · write | 0 | USD/write |
| Planning allocation · one copy | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · one copy | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · one copy | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · one copy | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · one copy | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · one copy | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · one copy | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · one copy | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · one copy | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · one copy | Target price guess · input token | 0 | USD/input token |
| Planning allocation · one copy | Target price guess · output token | 0 | USD/output token |
| Planning allocation · one copy | Approximate target service minimum | 0 | USD/month |
| Planning allocation · one copy | Minimum primary CPU | 2 | vCPU |
| Planning allocation · one copy | Minimum primary RAM | 8 | GiB |
| Planning allocation · one copy | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · one copy | Additional full-price standby copy | 0 | 0 or 1 |
| Planning allocation · one copy | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · one copy | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · one copy | Planning peak / mean work | 2 | multiplier |
| Planning allocation · one copy | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · one copy | Planning disk utilization | 0.7 | fraction |
| Planning allocation · one copy | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · one copy | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · one copy | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · one copy | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink write price guess | 0.000005 | USD/write |
| Planning allocation · two copies | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · two copies | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · two copies | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · two copies | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · two copies | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · two copies | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · two copies | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · two copies | Target CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · two copies | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · two copies | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · two copies | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · two copies | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · two copies | Target price guess · read | 0 | USD/read |
| Planning allocation · two copies | Target price guess · write | 0 | USD/write |
| Planning allocation · two copies | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · two copies | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · two copies | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · two copies | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · two copies | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · two copies | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · two copies | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · two copies | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · two copies | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · two copies | Target price guess · input token | 0 | USD/input token |
| Planning allocation · two copies | Target price guess · output token | 0 | USD/output token |
| Planning allocation · two copies | Approximate target service minimum | 0 | USD/month |
| Planning allocation · two copies | Minimum primary CPU | 2 | vCPU |
| Planning allocation · two copies | Minimum primary RAM | 8 | GiB |
| Planning allocation · two copies | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · two copies | Additional full-price standby copy | 1 | 0 or 1 |
| Planning allocation · two copies | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · two copies | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · two copies | Planning peak / mean work | 2 | multiplier |
| Planning allocation · two copies | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · two copies | Planning disk utilization | 0.7 | fraction |
| Planning allocation · two copies | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · two copies | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · two copies | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · two copies | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink write price guess | 0.000005 | USD/write |
* Only the selected native meter varies; other usage quantities and assumptions retain their displayed defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
* Unit prices and capacity coefficients are editable authored planning guesses, not verified provider tariffs or measured capacity.
* The origin is the exact registered google::1.0.0::memorystore::redis identity. Renamed products and future aliases require explicit mapping updates.
* Source allocated CPU-hours and memory-hours establish independent minimum target allocation. Neither management API requests nor a key-operation count is an instance count.
* Peak weighted key-operation work and resident data can promote the allocation above those minima. CPU rounds to whole cores and RAM to quarter GiB.
* CPU and RAM are aggregate resources over 730 hours. Selected backend tariffs own replica count, availability configuration and actual instance shapes.
* A multi-core estimate assumes the workload can be partitioned. Redis command execution, hot keys, cross-key transactions and clustering can prevent linear scale.
* Zero allocated resources and zero workload do not prove target scale-to-zero; the selected backend may retain a provisioned minimum.
* All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
* Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification.
* Cache storedGiB represents resident RAM footprint, not billable SSD. Persistence, snapshots and backup disks require a separate explicit allocation.
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.
Excluded costs and workload features:
* Replication traffic, snapshots, persistence write IOPS, network egress, cluster management premiums, licenses and migration.
* Command-specific complexity, Lua/scripts, module behavior, eviction/expiry churn, blocking commands, multi-key locality and benchmark-qualified latency.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.
Planning assumptions authored: 2026-10-18. Model: `plan-a5dd44a392cc5d4a1c85d03f803d3dc9f6e65da4` / `2026-10-18.planning.1`. Curve: `workload-3`.
### Google Memorystore Redis allocated cache capacity · Allocated source cache CPU-hours
**Planning estimate with editable assumptions.** These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available.
Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.
Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more.
Estimated allocation from planning assumptions; not benchmark calibrated. Only discrete samples are shown. Unpriced means no target quote or cost difference is available within the sizing policy.
| Allocated source cache CPU-hours (vCPU-hour/month) | Origin | Target scenario | Target | Difference |
| -: | -: | - | -: | -: |
| 0 | 87.6 | Planning allocation · one copy | 113.515 | 25.915 |
| 0 | 87.6 | Planning allocation · two copies | 227.03 | 139.43 |
| 730 | 124.1 | Planning allocation · one copy | 113.515 | -10.585 |
| 730 | 124.1 | Planning allocation · two copies | 227.03 | 102.93 |
| 1460 | 160.6 | Planning allocation · one copy | 216.08 | 55.48 |
| 1460 | 160.6 | Planning allocation · two copies | 432.16 | 271.56 |
| 5840 | 379.6 | Planning allocation · one copy | 864.32 | 484.72 |
| 5840 | 379.6 | Planning allocation · two copies | 1728.64 | 1349.04 |
| 23360 | 1255.6 | Planning allocation · one copy | 3457.28 | 2201.68 |
| 23360 | 1255.6 | Planning allocation · two copies | 6914.56 | 5658.96 |
| 93440 | 4759.6 | Planning allocation · one copy | Unpriced | Unavailable |
| 93440 | 4759.6 | Planning allocation · two copies | Unpriced | Unavailable |
**Estimated allocation from planning assumptions; not benchmark calibrated.**
The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload's assumptions define the translation. HA changes pricing, not this policy's throughput estimate. Unpriced workloads exceed the policy's configuration range; no silent vertical cap or automatic sharding is assumed.
| Sample / scenario | Basis | Mean / peak work/s | Required vCPU | Allocated vCPU | Memory GiB | SSD GiB | Resident GiB | Policy | Constraints |
| - | - | -: | -: | -: | -: | -: | -: | - | - |
| 0 vCPU-hour/month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 2 | 2 | 9.25 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 0 vCPU-hour/month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 2 | 2 | 9.25 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 730 vCPU-hour/month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 2 | 2 | 9.25 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 730 vCPU-hour/month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 2 | 2 | 9.25 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1460 vCPU-hour/month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 1460 vCPU-hour/month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 3 | 4 | 16 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 5840 vCPU-hour/month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 10 | 16 | 64 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 5840 vCPU-hour/month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 10 | 16 | 64 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 23360 vCPU-hour/month / Planning allocation · one copy | PlanningAssumption | 110 / 220 | 37 | 64 | 256 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 23360 vCPU-hour/month / Planning allocation · two copies | PlanningAssumption | 110 / 220 | 37 | 64 | 256 | 0 | 6 | `service-adapter-planning-2026-10-18.1` | None reported |
| 93440 vCPU-hour/month / Planning allocation · one copy | Unpriced | 110 / 220 | 148 | Unpriced | Unpriced | Unpriced | 6 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
| 93440 vCPU-hour/month / Planning allocation · two copies | Unpriced | 110 / 220 | 148 | Unpriced | Unpriced | Unpriced | 6 | `service-adapter-planning-2026-10-18.1` | Demand exceeds the planning model's joint CPU/RAM allocation bounds (96 vCPU, 624 GiB RAM). |
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
**Curve assumptions**
| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Planning allocation · one copy | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · one copy | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · one copy | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · one copy | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · one copy | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · one copy | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · one copy | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · one copy | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · one copy | Target CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · one copy | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · one copy | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · one copy | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · one copy | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · one copy | Target price guess · read | 0 | USD/read |
| Planning allocation · one copy | Target price guess · write | 0 | USD/write |
| Planning allocation · one copy | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · one copy | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · one copy | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · one copy | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · one copy | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · one copy | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · one copy | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · one copy | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · one copy | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · one copy | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · one copy | Target price guess · input token | 0 | USD/input token |
| Planning allocation · one copy | Target price guess · output token | 0 | USD/output token |
| Planning allocation · one copy | Approximate target service minimum | 0 | USD/month |
| Planning allocation · one copy | Minimum primary CPU | 2 | vCPU |
| Planning allocation · one copy | Minimum primary RAM | 8 | GiB |
| Planning allocation · one copy | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · one copy | Additional full-price standby copy | 0 | 0 or 1 |
| Planning allocation · one copy | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · one copy | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · one copy | Planning peak / mean work | 2 | multiplier |
| Planning allocation · one copy | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · one copy | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · one copy | Planning disk utilization | 0.7 | fraction |
| Planning allocation · one copy | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · one copy | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · one copy | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · one copy | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · one copy | Dependent object sink write price guess | 0.000005 | USD/write |
| Planning allocation · two copies | Origin price guess · Allocated Redis CPU | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Origin price guess · Allocated Redis memory | 0.015 | USD/GiB-hour |
| Planning allocation · two copies | Origin price guess · Average resident Redis data | 0 | USD/GiB-month |
| Planning allocation · two copies | Origin price guess · Redis key reads | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Redis key writes | 0 | USD/Operations |
| Planning allocation · two copies | Origin price guess · Cache management requests | 0 | USD/Requests |
| Planning allocation · two copies | Target / origin allocated resources | 1.15 | multiplier |
| Planning allocation · two copies | Read CPU work per key read | 1 | equivalents/read |
| Planning allocation · two copies | Write CPU work per key write | 2 | equivalents/write |
| Planning allocation · two copies | Planning key-operation throughput per vCPU | 10000 | equivalents/vCPU-second |
| Planning allocation · two copies | Target CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Peak / mean key-operation traffic | 2 | multiplier |
| Planning allocation · two copies | Physical memory per logical resident GiB | 1.5 | multiplier |
| Planning allocation · two copies | Usable cache memory fraction | 0.7 | fraction |
| Planning allocation · two copies | Minimum RAM per selected CPU | 4 | GiB/vCPU |
| Planning allocation · two copies | Maximum RAM per selected CPU | 8 | GiB/vCPU |
| Planning allocation · two copies | Target price guess · read | 0 | USD/read |
| Planning allocation · two copies | Target price guess · write | 0 | USD/write |
| Planning allocation · two copies | Target price guess · provider operation | 0 | USD/provider operation |
| Planning allocation · two copies | Target price guess · GiB-month | 0 | USD/GiB-month |
| Planning allocation · two copies | Target price guess · published GiB | 0 | USD/published GiB |
| Planning allocation · two copies | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Planning allocation · two copies | Target price guess · network GiB | 0.09 | USD/network GiB |
| Planning allocation · two copies | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Planning allocation · two copies | Target price guess · vCPU-hour | 0.05 | USD/vCPU-hour |
| Planning allocation · two copies | Target price guess · GiB-hour | 0.006 | USD/GiB-hour |
| Planning allocation · two copies | Target price guess · resource-hour | 0 | USD/resource-hour |
| Planning allocation · two copies | Target price guess · resource-month | 0 | USD/resource-month |
| Planning allocation · two copies | Target price guess · input token | 0 | USD/input token |
| Planning allocation · two copies | Target price guess · output token | 0 | USD/output token |
| Planning allocation · two copies | Approximate target service minimum | 0 | USD/month |
| Planning allocation · two copies | Minimum primary CPU | 2 | vCPU |
| Planning allocation · two copies | Minimum primary RAM | 8 | GiB |
| Planning allocation · two copies | Modeled cache SSD allocation (excluded) | 0 | GiB |
| Planning allocation · two copies | Additional full-price standby copy | 1 | 0 or 1 |
| Planning allocation · two copies | Allocated share of provisioned cost | 1 | fraction |
| Planning allocation · two copies | Planning read/write work per vCPU-second | 1000 | operations/vCPU-second |
| Planning allocation · two copies | Planning peak / mean work | 2 | multiplier |
| Planning allocation · two copies | Planning primary CPU utilization | 0.7 | fraction |
| Planning allocation · two copies | Resident state reserved in RAM | 0 | fraction |
| Planning allocation · two copies | Planning disk utilization | 0.7 | fraction |
| Planning allocation · two copies | Maintenance and log disk reserve | 0 | GiB |
| Planning allocation · two copies | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Planning allocation · two copies | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Planning allocation · two copies | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Planning allocation · two copies | Dependent object sink write price guess | 0.000005 | USD/write |
* Only the selected native meter varies; other usage quantities and assumptions retain their displayed defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
* Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
* Unit prices and capacity coefficients are editable authored planning guesses, not verified provider tariffs or measured capacity.
* The origin is the exact registered google::1.0.0::memorystore::redis identity. Renamed products and future aliases require explicit mapping updates.
* Source allocated CPU-hours and memory-hours establish independent minimum target allocation. Neither management API requests nor a key-operation count is an instance count.
* Peak weighted key-operation work and resident data can promote the allocation above those minima. CPU rounds to whole cores and RAM to quarter GiB.
* CPU and RAM are aggregate resources over 730 hours. Selected backend tariffs own replica count, availability configuration and actual instance shapes.
* A multi-core estimate assumes the workload can be partitioned. Redis command execution, hot keys, cross-key transactions and clustering can prevent linear scale.
* Zero allocated resources and zero workload do not prove target scale-to-zero; the selected backend may retain a provisioned minimum.
* All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
* Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification.
* Cache storedGiB represents resident RAM footprint, not billable SSD. Persistence, snapshots and backup disks require a separate explicit allocation.
* Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* Cache resident GiB is RAM provenance. Family-selected RAM-hours cover the working set;
* no SSD allocation is modeled. Persistence, snapshots and backup disks remain excluded.
Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.
Excluded costs and workload features:
* Replication traffic, snapshots, persistence write IOPS, network egress, cluster management premiums, licenses and migration.
* Command-specific complexity, Lua/scripts, module behavior, eviction/expiry churn, blocking commands, multi-key locality and benchmark-qualified latency.
* Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
* Unmodeled dependent services, task execution and operations outside the selected workload family.
Planning assumptions authored: 2026-10-18. Model: `plan-a5dd44a392cc5d4a1c85d03f803d3dc9f6e65da4` / `2026-10-18.planning.1`. Curve: `workload-4`.
See the [service catalog](/byoc/service-adapters/catalog) for operation coverage, supported directions and backend limitations.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.
