DockHosting Docs
GitHubGitHub
  • Introduction
  • Quick Start
    • Create an Account
    • Create a Project
    • Add a Database
    • Add a Domain
    • Use the CLI
  • Core Concepts
  • Deploying Apps
    • Deploy Lifecycle
    • Frameworks
    • Environment Variables
    • Logs
    • Scale to Zero
    • GitHub Deploys
    • Dockerfile Deploys
  • Databases
    • Engines
    • Create a Database
    • Connect
    • Public Access
    • Firewall
    • Backups
    • Admin Panels
    • Resize
  • Domains
    • Free Subdomains
    • Custom Domains
    • DNS Records
    • SSL
    • Troubleshooting
  • Billing & Tokens
    • Tokens
    • Costs
    • Top Up
    • Auto Top-Up
    • Low Balance
  • CLI
    • dock login
    • dock logout
    • dock whoami
    • dock help
    • dock deploy
    • dock link
    • dock ls
    • dock info
    • dock open
    • dock logs
    • dock start
    • dock stop
    • dock restart
    • dock rm
    • dock env
    • dock run
    • dock shell
    • dock tokens
    • dock context
    • dock update
    • dock completion
    • dock db
  • Reference
  • Troubleshooting
  • Contact

On This Page

  • When to resize
  • What to check first
  • After resizing
Question? Give us feedback →Edit this page
DatabasesResize

Resize a Database

Resize when the database needs more CPU, memory, or storage.

When to resize

  • CPU stays high during normal traffic.
  • Queries are slow because memory is too low.
  • Storage is close to full.
  • Connection count is consistently high.

What to check first

Before resizing, check whether slow queries, missing indexes, or a traffic spike are the real cause.

After resizing

Watch metrics for CPU, RAM, connections, and disk to confirm the new size helped.

Admin PanelsDomains

Copyright 2026 DockHosting dockhosting.dev contact@dockhosting.dev