---
title: Manually change compute resources | Tiger Data Docs
description: Resize compute resources for your Tiger Cloud service with minimal downtime
---

Tiger Cloud charges are based on the amount of storage you use. You don’t pay for fixed storage size, and you don’t need to worry about scaling disk size as your data grows, we handle it all for you. To reduce your data costs further, combine [hypercore](/docs/reference/timescaledb/hypercore/index.md), a [data retention policy](/docs/learn/data-lifecycle/data-retention/about-data-retention/index.md), and [tiered storage](/docs/learn/data-lifecycle/storage/about-storage-tiers/index.md).

You use [Tiger Console](https://console.cloud.tigerdata.com/) to resize the compute (CPU/RAM) resources available to your Tiger Cloud services at any time, with a short downtime.

## Update compute resources for a service

You can change the CPU and memory allocation for your standard service at any time with minimal downtime, usually less than a minute. The new resources become available as soon as the service restarts. You can change the CPU and memory allocation up or down, as frequently as required.

![Change resources](/docs/_astro/tiger-console-update-cpu-manually.DRnZv6ev_Ze3Xpb.webp)

To change the resources of a free service, first [convert it to a standard one](/docs/deploy/tiger-cloud/tiger-cloud-aws/service-management/service-management#convert-a-free-service-to-a-standard-one/index.md).

Note that:

- For the 48 CPU / 192 GiB option, 6 CPU / 14 GiB is reserved for platform operations.
- For the 64 CPU / 256 GiB option, 6 CPU / 16 GiB is reserved for platform operations.

There is momentary downtime while the new compute settings are applied. In most cases, this is less than a minute. However, before making changes to your service, best practice is to enable [HA replication](/docs/deploy/tiger-cloud/tiger-cloud-aws/high-availability/overview/index.md) on the service. When you resize a service with HA enabled, Tiger Cloud:

1. Resizes the replica.
2. Waits for the replica to catch up.
3. Performs a switchover to the resized replica.
4. Restarts the primary.

HA reduce downtime in the case of resizes or maintenance window restarts, from a minute or so to a couple of seconds.

When you change resource settings, the current and new charges are displayed immediately so that you can verify how the changes impact your costs.

Warning

Because compute changes require an interruption to your services, plan accordingly so that the settings are applied during an appropriate service window.

1. **In Console, choose the service to modify**

2. **Click `Operations` > `Compute and storage`**

3. **Select the new `CPU / Memory` allocation**

   You see the allocation and costs in the comparison chart.

4. **Click `Apply`**

   Your service goes down briefly while the changes are applied.

## Out of memory errors

If you run intensive queries on your standard services, you might encounter out of memory (OOM) errors. This occurs if your query consumes more memory than is available.

When this happens, an `OOM killer` process shuts down PostgreSQL processes using `SIGKILL` commands until the memory usage falls below the upper limit. Because this kills the entire server process, it usually requires a restart.

To prevent service disruption caused by OOM errors, Tiger Cloud attempts to shut down only the query that caused the problem. This means that the problematic query does not run, but that your service continues to operate normally.

- If the normal OOM killer is triggered, the error log looks like this:

  ```
  2021-09-09 18:15:08 UTC [560567]:TimescaleDB: LOG: server process (PID 2351983) was terminated by signal 9: Killed
  ```

  Wait for the service to come back online before reconnecting.

- Tiger Cloud shuts the client connection only

  If Tiger Cloud successfully guards the service against the OOM killer, it shuts down only the client connection that was using too much memory. This prevents the entire service from shutting down, so you can reconnect immediately. The error log looks like this:

  ```
  2022-02-03 17:12:04 UTC [2253150]:TimescaleDB: tsdbadmin@tsdb,app=psql [53200] ERROR: out of memory
  ```

If you encounter OOM errors on a free service, [convert it to a standard service](/docs/deploy/tiger-cloud/tiger-cloud-aws/service-management/service-management#convert-a-free-service-to-a-standard-one/index.md), then increase its CPU and memory allocation as needed to resolve the memory pressure.