CoreCluster · Protect

Capacity

See what your sites really use against the package, and upgrade before anything is refused.

manage.corefinity.com/managed-clusters
Capacity Brindlewyck UK · UK · CC8
Usage history Upgrade package

What your sites and environments use, measured at their busiest over 24 h, against the package.

CPU26%

2.1 / 8 cores

Memory71%

22.6 / 32 GB

Storage53%

212 / 400 GB

warns at 75% · new sites pause at 90%

Needs attention 2
27 healthy 1 applying 1 degraded
  • !
    fernglimmer.co.uk PHP restarted after running out of memory
    Degraded Acknowledge
  • ⟳
    fellstride-outdoors.co.uk PHP 8.2 → 8.3, back in about a minute
    Applying Open

Measured on real use, not allocations, so a cluster carries more sites than the arithmetic suggests.

{  How it works  }

Capacity, step by step

  1. 1

    Three meters per cluster

    CPU and memory count each site’s busiest moments over the last 24 hours. Disk counts what is provisioned.

    manage.corefinity.com/managed-clusters
    The Capacity card: CPU, memory and storage meters with the 75% and 90% lines
  2. 2

    An amber warning at 75%

    Past 75% on any meter, the card says upgrade soon. At 90%, new sites and environments wait until you upgrade.

    manage.corefinity.com/managed-clusters
    Capacity What the cluster’s sites and environments use against the CC8 package.
    CC8 · 8 cores · 32 GB
    !

    Upgrade soon: memory is at 78% of the package. New sites are still allowed until 90%.

    Upgrade package
    CPU41%

    3.3 / 8 cores

    Memory78%

    25 / 32 GB · upgrade soon

    Storage53%

    212 / 400 GB provisioned

    75% · upgrade soon   90% · new sites and environments stop

  3. 3

    Needs attention tells you

    A full meter, a site near its limit or a failed task is listed on the dashboard, most urgent first.

    manage.corefinity.com/managed-clusters
    Needs attention 3
    Most urgent first
    • !
      Disk nearly full plinthwick.studio

      Disk is 96% full (28.8 of 30 GB).

      12 min agoOpen siteAcknowledge
    • !
      Memory at 78% Brindlewyck UK

      Brindlewyck UK uses 25 of 32 GB over the last 24 h. Consider a bigger package.

      1 h agoUpgrade packageAcknowledge
    • !
      PageSpeed dropped kilnandcopse.com

      Mobile performance dropped 18 points this week (74 → 56).

      Today 03:10Open siteAcknowledge
    Acknowledged (2) If a problem clears and comes back, it shows again.
  4. 4

    Upgrade the package

    Pick a bigger package and type the cluster name. Capacity grows straight away and nothing restarts.

    manage.corefinity.com/managed-clusters
    Upgrade package — Brindlewyck UK Pick a bigger package. Capacity grows straight away; nothing restarts.
    CurrentCC88 cores · 32 GB · 400 GB storage · 800 GB snapshots
    CC1212 cores · 48 GB
    600 GB storage · 1,200 GB snapshots Memory now 78% → 52%
    CC1616 cores · 64 GB
    800 GB storage · 1,600 GB snapshots Memory now 78% → 39%
    Type Brindlewyck UKBrindlewyck UK Cancel Upgrade to CC12
manage.corefinity.com/managed-clusters
The Capacity card: CPU, memory and storage meters with the 75% and 90% lines
manage.corefinity.com/managed-clusters
Capacity What the cluster’s sites and environments use against the CC8 package.
CC8 · 8 cores · 32 GB
!

Upgrade soon: memory is at 78% of the package. New sites are still allowed until 90%.

Upgrade package
CPU41%

3.3 / 8 cores

Memory78%

25 / 32 GB · upgrade soon

Storage53%

212 / 400 GB provisioned

75% · upgrade soon   90% · new sites and environments stop

manage.corefinity.com/managed-clusters
Needs attention 3
Most urgent first
  • !
    Disk nearly full plinthwick.studio

    Disk is 96% full (28.8 of 30 GB).

    12 min agoOpen siteAcknowledge
  • !
    Memory at 78% Brindlewyck UK

    Brindlewyck UK uses 25 of 32 GB over the last 24 h. Consider a bigger package.

    1 h agoUpgrade packageAcknowledge
  • !
    PageSpeed dropped kilnandcopse.com

    Mobile performance dropped 18 points this week (74 → 56).

    Today 03:10Open siteAcknowledge
Acknowledged (2) If a problem clears and comes back, it shows again.
manage.corefinity.com/managed-clusters
Upgrade package — Brindlewyck UK Pick a bigger package. Capacity grows straight away; nothing restarts.
CurrentCC88 cores · 32 GB · 400 GB storage · 800 GB snapshots
CC1212 cores · 48 GB
600 GB storage · 1,200 GB snapshots Memory now 78% → 52%
CC1616 cores · 64 GB
800 GB storage · 1,600 GB snapshots Memory now 78% → 39%
Type Brindlewyck UKBrindlewyck UK Cancel Upgrade to CC12
{  What you can set  }

Options and limits

Everything here is per site or per environment, from the panel, with every change in the activity log.

Measured
CPU and memory at their busiest over the last 24 hours, not what is allocated.
Storage
The disk the sites and environments provision, against the package allowance.
Upgrade soon
Any meter at 75% turns amber and is listed on Needs attention.
New sites pause
At 90%, new sites and environments are refused. Running sites carry on.
Sites per cluster
No fixed number. What the sites use is what counts.
Upgrades
From the cluster page, in a few clicks. Moving up from CC4 restarts each environment once.
Downgrades
Done by Corefinity. Ask support.
History
Usage charts per cluster and per site, from 6 hours to 30 days.

Questions about capacity

Nothing stops. Sites already running carry on as before. New sites and environments are refused at 90% until you upgrade the package or remove something.

No. Capacity grows straight away and nodes are added as sites need them. The one exception is moving up from CC4, which changes node size, so each environment restarts once, one at a time.

Most sites are quiet most of the time. Counting what they use at their busiest, rather than what they could use, lets one cluster carry more sites.

{  CoreCluster  }

See capacity on your own cluster

Tell us how many sites you run and on what. An engineer sizes a cluster with you and shows you the panel on a live one.

By sending this message you agree to our Privacy Policy .