How the shared resource pool works on Schokr
Schokr gives each team one pool of memory, CPU and disk. Learn how to split it across up to 4 servers and rebalance it later.
Updated · 2 min read
On Schokr, resources belong to your team, not to individual servers. Your team has one pool of memory, CPU and disk, and every server you create takes a share of it. You choose how big each share is.
The pool
With the free package, a team's pool is:
- Memory: 6144 MiB (6 GB)
- CPU: 150% (1.5 cores)
- Disk: 10240 MiB (10 GB)
- Server slots: 4
Store upgrades you buy with credits are added to this same pool.
Example splits
Here are a few ways teams commonly split the free pool:
| Setup | Memory | CPU | Disk |
|---|---|---|---|
| One Minecraft server | 6144 MiB | 150% | 10240 MiB |
| Minecraft + Discord bot | 5120 + 1024 MiB | 120% + 30% | 8192 + 2048 MiB |
| Four small bots | 4 x 1536 MiB | 4 x 37% | 4 x 2560 MiB |
| Game server + voice + 2 bots | 4096 + 512 + 2 x 768 MiB | 100% + 20% + 2 x 15% | 7168 + 1024 + 2 x 1024 MiB |
These are starting points. Check what your server actually uses in the console and adjust.
How much does each kind of server need?
Rough guidance:
- Discord bots (Node.js, Bun, Python): small bots often run in 256 to 512 MiB. Large bots with many guilds or caching need more.
- Minecraft Java: a small Paper server for a few friends is comfortable with 2 to 4 GB. Modded (Forge) servers usually want more.
- Voice servers: TeamSpeak 3 and Mumble are light and run in a few hundred MiB.
- Source and other games: depends heavily on the game, map and player count.
CPU is shared too. 100% equals one core. A server given 50% can use half a core at most, which may be fine for a bot but sluggish for a game.
Rebalancing later
You are not locked in. You can change any server's memory, CPU and disk later from its Resources section, as long as the total stays within your pool. To give one server more, lower another first. See changing a server's resources.
Tips
- Leave some headroom. A server that is right at its memory limit can be killed for running out of memory. See fixing out of memory errors.
- Disk includes everything: worlds, logs, plugins,
node_modules, Python packages and archives you create in the file manager. - Deleting a server frees its share back to the pool immediately.
- Each team has its own pool. If you are in two teams, resources do not move between them, but credits can be transferred between teams.