Resources Allocation Print

  • cloudlinux, inode, lve manager, cagefs, shared hosting, cpanel, directadmin
  • 9

Our in-house cloud infrastructure are purposely built and optimized for daily business use. Coupled with CloudLinux, it allow our web hosting services run in stable, secure and individual account isolated environment (CageFS - Visit HERE for more information). Your website no longer affected by noisy neighbors who possibly use up entire server resources that eventually bring down your website in the same machine.


Typical hosting: CPU=100%, Physical Memory=256MB, Disk IO=1024KB/s or 1MB/s
Highend hosting: CPU=200%, Physical Memory=512MB, Disk IO=1024KB/s or 1MB/s

Following tables indicate the allocated resources for each web hosting plans:

Service Plan
CPU Power (%)
Physical Memory (MB)
Disk IO (MB/s)
Inode Allocation
(Max. Files)
LVE Manager
for Reseller
Cloud Value
Default setting for
new account creation
on reseller & ESCloud plan.
100 384 8 80,000 n.a.
Cloud 30G 100 512 10 90,000 n.a.
Cloud 40G 110 512 10 100,000 n.a.
Cloud 50G 120 768 12 110,000 n.a.
Biz Value 130 1024 15 110,000 n.a.
CloudBiz 1 140 1280 15 120,000 n.a.
CloudBiz 2 150 1536 18 130,000 n.a.
CloudBiz 3 200 2048 20 150,000 n.a.
ESCloud 1 100 1024 30 300,000 Included
ESCloud 2 200 2048 40 400,000 Included
ESCloud 3 200 3072 40 500,000 Included
ESCloud 4
300 4096 50 600,000 Included
100 384 8 100,000 n.a.
BizMail2 100 384 8 120,000 n.a.
BizMail3 150 512 10 150,000 n.a.
BizMail4 150 512 10 200,000 n.a.
  • For server stability, we reserved the rights to change above allocated resources value without prior notice.

    1) Speed (CPU Power)
    Percentage of CPU power allocated. Eg. suppose one CPU core = 2GHz, with CPU power of 50% means you can use up to 1GHz CPU power to run your website. 100% means full one core or 2GHz. If your CPU usage go beyond the limit, your website will slow down or stop working. HOWEVER, other tenant's website remain normal.

    2) Physical / Virtual Memory
    Amount of memory that allocated for each account. If your memory usage go beyond the limit, visitors to your site will receive error 500 or error 503 message in their web browser.

    3) Disk I/O
    This parameter is the restriction of data throughput for each hosting account. When website data throughput go beyond the limit, your website will still working but at slower rate until the active data flow level lower than the limit set. 10sec burst through the limit is enabled for each account.

    4) LVE Manager for Reseller
    This is additional feature for reseller under our Elastic Cloud Web Hosting plans, where reseller able to adjust the resources package for each of their users account. You can upgrade your current reseller plan (which going to phase out soon) to our ESCloud plan.

    5) Inode Allocation
    Eash hosting plan allocated with number of inode, which usually refers to as the number of files permitted in each hosting plan. This including email, web content and logs. In order to avoid hitting the limit, you're always advise to upkeep your files, especially email. You will experience unable to upload, unable to receive email or change web content when inode exceeded the permissible limit, and it is time to upgrade your hosting plan.


    When your website hits the pre-allocated resources limit based on above service plans, you will observed abnormal respond of your website.
    You can always login to your cPanel account and look for Metrics >> CPU & Concurrent Connection Usage. You can view details of resources usage in graphical form as well as raw data for each interval.

    What you can do?
    1) Check your website content to see any poorly written scripts.
    2) Repair / optimize your database.
    3) Disable plugins or features that causes over usage of resources.
    4) Order new cloud hosting plan or Elastic Web Hosting plan and split your domain(s) to different account (Since resources limit is per cPanel account basis). You can also upgrade to Reseller Hosting for the same purpose.
    5) Upgrade to higher plan based on your website resources usage historical data.
    6) Move to higher level - Cloud VM or VPS.

Was this answer helpful?

« Back