Call of Duty 4 Starter · 2 GB
€2.14 / month
- vCPU
- 2 cores
- RAM
- 2 GB
- Storage
- 30 GB SSD
- Processor
- Intel Xeon E5-2699 v4
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Selectable operating system
FPS · PC
Call of Duty 4 planning covers slots, game mode, map rotation, PunkBuster or administration scope, mods, and recording.
€2.14 / month
€3.03 / month
€4.10 / month
€5 / month
€7.14 / month
A full match with dense explosions and kill events plus mod scripts peaks above an idle server.
The first resource profile for a controlled launch and measurement baseline.
A middle profile to assess as community and content workload grows.
A higher resource profile to compare when measured CPU, RAM or storage needs increase.
Evaluate CPU, memory, and storage options against the expected game workload.
Treat players and spectators with the mode; a small Search and Destroy match differs from a crowded fast-respawn mode.
Measure processor peaks and game-loop response during a busy session.
Track peak memory use together with growth headroom.
Measure storage behaviour across saves, logs, and backups.
Measure actual mod, plugin, and script workload separately from extension count.
Track world size, active regions, and persistent-data growth together.
Evaluate concurrent-player distribution, activity, and content workload together.
| Scenario | Resource effect | Check |
|---|---|---|
| Concurrent players | Treat players and spectators with the mode; a small Search and Destroy match differs from a crowded fast-respawn mode. | Measure a busy session |
| Game activity | A full match with dense explosions and kill events plus mod scripts peaks above an idle server. | Repeat the peak scenario |
| World / save growth | Logs, demos, bans, and mod files accumulate; set retention around league or community record needs. | Track save and restore duration |
Estimate starting capacity from your player and world goals.
Estimated CPU, memory, storage, and a suitable resource profile appear here.
Serve mod folders, fast-download content, and custom maps in compatible versions and test rotation changes.
Mod compatibility can vary by game and server-software release.
Keep gametype, map rotation, PunkBuster state, RCON, mod path, rate, and reserved slots in one server profile.
After deployment, manage Call of Duty 4 processes, version changes, and settings that require restarts in controlled maintenance windows.
Back up Call of Duty 4 saves, configuration, and additional-content data as separate restore points before changes.
Limit file access to Call of Duty 4 configuration, logs, and managed content directories; stop the relevant process before replacing active files.
Define the gametype, maps and custom mods first. Measure a small Search and Destroy session separately from a busy fast-paced mode rather than applying one player target to every scenario.
Use the intended match’s player and spectator mix in the test. Observe CPU, memory and connection behaviour during busy combat instead of deriving a capacity guarantee from idle results.
Match the mod folder, files distributed to clients and map versions. Test a new player joining and a rotation transition, confirming prepared installation or content rights separately.
Account for retained demos, logs and ban data separately from mod files. Set retention around league review needs and keep required evidence outside routine cleanup.
Record the gametype, map rotation, mod path, rate and reserved-slot settings with the working version. Transfer RCON access securely and verify the relevant client and server requirements in the new environment.
Contact support for ordering details and special requirements.