Turkey (Turkish)
Germany (German)
Worldwide (English)
Current Plesk Obsidian requirements list 1 GB RAM plus 1 GB swap for Linux and 2 GB RAM for Windows.
Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
Evaluate Plesk Obsidian RAM, per-site memory, IIS/PHP-FPM, mail, Docker and disk sizing for Linux and Windows production.
Current Plesk Obsidian requirements list 1 GB RAM plus 1 GB swap for Linux and 2 GB RAM for Windows.
Plesk also provides rough guidance of 1 GB RAM per 40-50 low-traffic shared sites and notes that higher-traffic sites may need 500 MB-1 GB per site.
1 GB Linux or 2 GB Windows is not production hosting capacity. Web server, database, mail, antivirus, backups and application runtimes quickly increase memory requirements.
On Linux, Nginx/Apache, PHP-FPM, MySQL/MariaDB, Postfix/Dovecot and Plesk services can share one node. Multiple PHP versions and many active FPM pools can increase idle memory.
WordPress Toolkit, malware scanners and Docker extensions require additional headroom beyond the minimum.
On Windows Plesk, IIS application pools and .NET applications can create separate worker processes per site. Many active pools can grow memory differently from shared PHP workloads on Linux.
If Windows Update, Defender and SQL Server share the same node, size further upward. The 2 GB minimum is not a realistic production target for that setup.
Plesk documentation recommends 20 GB minimum and 50 GB for the root partition, while domains, mail, backups and databases under /var can grow rapidly. Inodes and I/O matter as much as raw capacity.
Plesk Cgroups Manager can limit customer CPU, RAM and disk read/write bandwidth on Linux. This reduces noisy-neighbor effects but cannot fix an undersized physical node.
Small Linux Plesk: 2-4 vCPU and 4-8 GB RAM. Small Windows Plesk: 4 vCPU and around 8 GB RAM for a more comfortable baseline. Multi-site/mail/DB: 8-16 cores and 16-32+ GB. These are production baselines, not vendor minimums.
free -hps --sort=-rss -eo pid,comm,rss,%mem | head -25df -hdf -iplesk bin server_pref --showPlesk's own per-site RAM guidance assumes low concurrency. WooCommerce, LMS, heavy mail, Elasticsearch/OpenSearch or Docker workloads can require far more at the same site count.
| Scenario | CPU | RAM | Key service |
|---|---|---|---|
| Small Linux Plesk | 2-4 vCPU | 4-8 GB | PHP-FPM + MariaDB |
| Small Windows Plesk | 4 vCPU | 8 GB | IIS + Defender |
| Busy multi-site | 8-16 cores | 16-32+ GB | DB + mail + workers |
Do not confuse minimum system requirements with production capacity. Evaluate peak workload, backups, growth headroom, resource-sharing policy and recovery planning together.
It is the official minimum, but very constrained once web, database and mail services run.
Usually Linux can start with lower baseline usage, but real consumption depends on IIS/.NET, mail, databases and workload.
Evaluate CPU, RAM, storage, network and operations together; buying a larger plan without identifying the bottleneck is rarely a durable fix.