Lab sizing

Lab sizing sets how much CPU and memory each machine lab gets, separately for every plan. By the end of this page you will know how to read a lab's card, change a limit, and put it back.

Open it from Admin Panel → Platform → Lab sizing.

Turned on by whoever runs the server

Lab sizing appears in the sidebar only when it is enabled in the platform's server configuration. If you do not see it, ask whoever runs the server.

Shown on labs.selfmade.ninja, the Selfmade Ninja Academy platform. On your own platform you will see your own domain and data.

Reading the page

This server says how many cores and how much memory the server has, and how much one lab may use at most. The rest is kept for the platform itself.

Below it is one card per machine lab, with the lab's name and id, for example Docker Lab docker. A lab made with the template builder shows a custom template badge and a shortened id; hover over the id to see all of it.

Only labs that are installed on this server are listed. A lab that is in the catalog but not yet installed has nothing to size, so it does not appear.

Each card has one box per plan:

Plan	Applies to
Free	Free accounts
Paid	Paid accounts
Admin	Platform administrators
Org	Labs deployed for an organization

Each box shows:

Field	What it means
Size, for example 4 CPU · 2g	What a deploy on that plan gets now
Badge workspace.json	The size comes from the range the lab's template allows
Badge template	The template sets one fixed size and no range
Badge your change	An admin set a limit on this page
cpu min … up to …, mem min … up to …	The range you can choose from. "Up to the whole server" means the template sets no ceiling

Change a limit

1. Find the lab's card and the plan's box.
2. Enter a CPU limit in cores, in steps of 0.5 (for example 2 or 1.5), a memory limit (for example 4g or 512m), or both.
3. Select Save. The box shows Saved — applies at next deploy, the page reloads, and the badge changes to your change.

To go back to the template's size, select Reset in that box.

A new limit applies at the next deploy

Labs that are already running keep the size they started with. The new limit applies the next time a lab of that kind is deployed or redeployed.

Limits you cannot cross

• Not below the lab's minimum. The template sets the least a lab needs to work. A smaller value is refused with the reason.
• Not above this server. One lab can never get more than the This server card allows.

Sizing a lab as you install it

When an administrator opens a machine lab in the Store, the lab's page shows the same per-plan boxes, so a lab can be sized right after it is installed.

Next

• Labs and instances: running labs across the platform
• Platform settings: modules and server-wide settings