2 - Apply Limits to Websites

Before reading this document you must read:

  1. [Introduction to Containerization (Website Limits)]1 - Introduction to Containerization (Website Limits))

To apply limits navigate to https://IP Of Your Server:8090/container/ . Once there click launch, so that you can manage limits for the site. Click Edit to set the limits. You will see default limits but they are not currently applied.


Limits Explained

You can apply 4 type of limits, and they are explained below.

CPU Percentage

Amount of CPU a certain website/user can use. On a Multi-core system user will get assigned share on each CPU Core. But CPU usage calculation will be divided by total cores on system. For example if website is assigned 10% CPU on a 4 core system, they will get 10% share of each CPU core.

If website start using 10% CPU on all 4 cores the average usage will then be 10% (40 / 4 = 10%)

Memory

Memory usage specifies the amount of RAM the website can use. User processes may be killed by kernel if they try to allocate more ram.

I/O

Disk I/O speed allowed for the website such as 10MB/s. This limit is not the same as IOPS described below.

IOPS

IOPS is different compared to IO, this specifies number of IO operations that a website user can do per second.

Network Speed

This specifies upload/download speed of the website user.

Hi, this is not available for ubuntu?

Thanks.

Not through CyberPanel as Ubuntu/Debian need a grub boot argument and some virtual servers don’t provide grub at all; thus it won’t work. On KVM-based or dedicated servers you can enable it and use it manually if you must: How to Limit CPU and Memory Usage With Cgroups on Debian/Ubuntu · GitHub

The real question is why does it require LSE when OLS also supports cgroups: Using cgroups v2 with OpenLiteSpeed – OpenLiteSpeed