Josh
c602b8f8f3
Discovery against the demo account on whp01 surfaced several inaccuracies: - Cache is Valkey (Redis wire-compatible), not Redis or Memcached. No Memcached is offered as a separate service. - Site Monitoring is the sidebar label (not 'AI Monitor'). - 'Add a domain' has no Primary/Add-on distinction. - Sites form: 'Container Type' (not 'Site type'), Number of Containers (1-10 for horizontal scaling), CPU per Container (default 0.25), Memory per Container (default 256MB), SSL inline on the same form. - Backups: default retention 5 days / 10 backups; on-demand + scheduled; S3 backup targets are visible and configurable. - Email: per-domain settings live behind 'Setup Instructions' on the Email page; mail server hostname is on the Dashboard (per-server, e.g. mail01.cloud-hosting.io), not per-domain. Also reworked the screenshot pipeline: - New shots.config.ts targets the real index.php?page=... URLs - Added redactSensitive() step that runs before each screenshot to swap server names, IPs, mail hostnames, and demo-user-isms with neutral placeholders. This keeps docs portable across the fleet. - Hides .brand-full and .navbar-text (top-bar server identifier and Welcome greeting). - Captured 9 real WHP screenshots; removed stale placeholders.
48 lines
2.2 KiB
Plaintext
48 lines
2.2 KiB
Plaintext
---
|
|
title: Resource upgrades
|
|
description: Add CPU, RAM, or disk to your container without migrating to a different plan.
|
|
sidebar:
|
|
order: 4
|
|
---
|
|
|
|
import PaidAddon from '~/content/partials/paid-addon-callout.mdx';
|
|
import Support from '~/content/partials/support-link.mdx';
|
|
|
|
<PaidAddon />
|
|
|
|
## What it does
|
|
|
|
Boost your container's **CPU**, **RAM**, or **persistent disk** without migrating to a new plan. Useful when you've outgrown your base allocation but the next plan tier up is more than you actually need.
|
|
|
|
## What you can upgrade
|
|
|
|
Each resource is independent — upgrade only what you need.
|
|
|
|
- **CPU cores per container** — visible on the Sites page as **CPU per Container (cores)** (default `0.25`). Add cores for sustained-compute workloads.
|
|
- **RAM per container** — visible on the Sites page as **Memory per Container (MB)** (default `256`). For memory-hungry apps (caches, large WordPress sites with many plugins, Node apps holding big in-memory state).
|
|
- **Number of containers** — scale a busy site horizontally from 1 up to 10 replicas; WHP load-balances traffic across them.
|
|
- **Persistent disk** — for sites that store a lot of files (media libraries, user uploads, etc.).
|
|
|
|
## When you might need this
|
|
|
|
- **High CPU on busy days.** Sustained-load sites consistently hit the per-container CPU cap during peak hours.
|
|
- **"Out of memory" errors** in your app log.
|
|
- **Disk usage approaching 80%** of your allocation. Get ahead of it — full disks cause backup failures and uploads to fail.
|
|
|
|
## How to enable
|
|
|
|
For per-container CPU/RAM upgrades, edit the values directly on the **Sites** page for the site you want to change, and click **Save**. For account-wide upgrades (more total RAM, more total disk), open the [client portal](https://secure.anhonesthost.com/clientarea.php), go to your hosting service → **Upgrade/Downgrade**, and pick the resource increment.
|
|
|
|
## See your current usage
|
|
|
|
Open the **Dashboard** page in WHP. The **Server Information** and account stats show what you're consuming. For per-site usage, open a site from the **Sites** page.
|
|
|
|
## Related
|
|
|
|
- [Site Monitoring](/whp/add-ons/monitoring/) — catches resource saturation before customers complain.
|
|
- [Add-ons overview](/whp/add-ons/overview/)
|
|
|
|
## Still stuck?
|
|
|
|
<Support />
|