Check and optimize

Every server starts with settings for its size, tested with real stores and sites. Your sites may need something different: more room for PHP’s code, more memory for a big database, or more PHP workers for a busy store. Check and optimize finds out from the server’s own week and suggests the changes.

Run the check

On the server’s page, click Check and optimize. (From a “nearly full” email or card, the button takes you straight there.)

It looks at the server’s last week of monitoring and its memory and database right now:

• PHP’s code cache: how full it is, and how much each site’s code takes
• PHP’s memory at its busiest, and whether sites had to wait for it
• whether sites hit their limit of PHP workers, and how busy the CPU was
• the database’s size, and how much of it is read from memory rather than disk

Then it shows what it found and the suggested changes, each with the reason. Nothing changes yet. Anyone on your team can run the check.

Apply the changes

Owners and admins can click Apply these changes. Before anything changes, it says what restarts: usually PHP (your sites pause for a second or two), sometimes the database (a few seconds). Then every site is checked to make sure it still works.

The new settings are kept as this server’s own, so later updates to the server’s setup keep them. Its “nearly full” alert closes right away; if it’s still short of room after half an hour of traffic, you’ll hear from us again.

Give it a day of normal traffic, then run the check again to see how the new settings are doing.

When settings can’t make enough room

Suggestions stay within limits we’ve tested for each server size. When that isn’t enough, the check says so and suggests what will: moving its biggest site to another server with room, or moving to a larger server.

Moving to another server size resets these settings to the new size’s own.