ISPmanager: Hardware requirements

From ISPWiki
Jump to: navigation, search

Server requirements

The ISPmanager control panel consumes low system resources and can be installed on any modern server or virtual machine given that an appropriate operating system is running on that server. Web-sites hosted on your server, however, may consume much resources. Before you choose a server, read the following information:

  • How many sites are you going to host on the server?

Servers that host multiple web-sites with databases and mail system, require more CPU power, RAM, and disk space.

  • What kind of sites will be hosted?

Servers that will host video and music, as well as high-volume web-sites (more than several thousands concurrent connections)require more RAM, CPU, and disk space.

Minimum hardware requirements

Server for personal use (ISPmanager Lite). A number of web-sites.

Component Minimum Recommended
CPU 226 MHz more than 1 GHz
Cores 1 more than 2
RAM 768 MB more than 2 Gb
Disk space 10 Gb more than 50 Gb

Server for shared hosting (ISPmanager Business). Multiple various web-sites, including high-volume sites.

Component Minimum Recommended
CPU 2,4 GHz more than 3 GHz
Cores 16 more than 24
RAM 32 Gb more than 64 Gb
Disk space 1 TB more than 2 TB

Disk subsystem

With ISPmanager, you can allocate all disk space available for the root filesystem (/)

You may change the partition, if needed. Please note that ISPmanager by default locates user data into /var/www (user disk quotas are set on the partition where user data are located), and the control panel is installed into /usr/local/mgr5/.


If you plan to use ISPmanager Business, all cluster nodes should locate in the same datacenter in one VLAN.

We recommend using two physical network interfaces for each node. Connect the first interface to public VLAN, and use public IP address. The second interface should be connected to internal VLAN with cluster nodes only. Use the internal network, e.g. When adding cluster nodes you should specify an IP address from the internal network to enhance cluster reliability and avoid network issues during migration.