Scale for Traffic

Temps lets you control how much CPU and memory each container gets, and how many containers (replicas) run for each environment. Scale vertically by increasing resources, or horizontally by adding replicas.

Check current resource usage

Before changing anything, check what your application is actually using.

1. Open your project in the dashboard
2. Click Monitoring in the project sidebar
3. Select the environment and container you want to inspect

The metrics dashboard shows real-time data via Server-Sent Events:

• CPU Usage — percentage of allocated CPU
• Memory Usage — bytes consumed and percentage of the memory limit
• Network Traffic — inbound and outbound data transfer rates

You can also get metrics from the API:

curl "https://your-temps-instance/api/projects/{project_id}/environments/{env_id}/containers/{container_id}/metrics" \
  -H "Authorization: Bearer YOUR_TOKEN"

Response:

{
  "cpu_percent": 45.2,
  "memory_bytes": 536870912,
  "memory_percent": 62.5,
  "memory_limit": 858993459,
  "network_rx_bytes": 1048576,
  "network_tx_bytes": 524288
}

Adjust CPU and memory limits

Resource limits are configured per environment. This lets you allocate more resources to production while keeping staging lightweight.

1. Open your project
2. Click Environments in the sidebar
3. Click on the environment you want to scale (e.g. production)
4. Go to Settings
5. Adjust the resource fields:

Click Save. Changes take effect on the next deployment. To apply immediately, click Redeploy on the current deployment.

Add replicas

Running multiple replicas of your application distributes load across containers. Temps' reverse proxy automatically load-balances requests across all healthy replicas.

To add replicas:

1. Go to your environment's Settings
2. Set Replicas to the desired count (e.g. 3)
3. Save and redeploy

What replicas share

• The same Docker image and environment variables
• The same linked managed services (database, Redis)
• The same domain and SSL certificate

What replicas do not share

• Memory and CPU — each replica has its own allocation
• Local filesystem — do not store state on disk; use the database or KV storage instead
• In-memory caches — each replica has its own memory space

Change the exposed port

If your application listens on a port other than 3000, configure it in the environment settings:

1. Go to your environment's Settings
2. Set Exposed Port to the port your application listens on
3. Save and redeploy

Temps resolves the port in this order:

1. EXPOSE directive in your Dockerfile
2. Exposed port setting on the environment
3. Exposed port setting on the project
4. Default: 3000

Scale via the API

Update environment settings programmatically:

curl -X PUT "https://your-temps-instance/api/projects/{project_id}/environments/{env_id}/settings" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "cpu_limit": 2000,
    "memory_limit": 1024,
    "replicas": 3,
    "exposed_port": 8080
  }'

After updating, trigger a redeploy for the changes to take effect.

When to scale up

Scaling your database

Managed services have their own resource configuration. If your PostgreSQL database is the bottleneck:

• Increase max_connections in the service settings
• Use connection pooling in your application (e.g. PgBouncer or built-in pool)
• Optimize slow queries using the data explorer in the dashboard