Skip to content

Conversation

@nkeshelava
Copy link

Add information about configuring a system-wide lower bound for pmem limit

Add information about configuring a system-wide lower bound for pmem limit
@nkeshelava nkeshelava marked this pull request as draft November 10, 2025 15:05
@annkots annkots marked this pull request as ready for review November 11, 2025 12:22
@annkots annkots marked this pull request as draft November 11, 2025 12:32

#### Physical memory lower bound

CloudLinux OS allows administrators to configure a lower bound (minimum value) for physical memory (PMEM) limits to prevent setting limits that are too low and could cause application instability. When a lower bound is configured, any attempt to set a PMEM limit below this threshold will be rejected with an error message. This helps ensure that hosting accounts always have sufficient memory allocated for basic application requirements, preventing performance issues and unexpected application failures. The lower bound is enforced system-wide and applies to all limit-setting operations, whether performed through command-line tools or control panel integrations.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will be rejected with an error message

"... displayed by CLI tool or Cloudlinux Manager UI".

This way we explain what to expect from UX standpoint.


#### Physical memory lower bound

CloudLinux OS allows administrators to configure a lower bound (minimum value) for physical memory (PMEM) limits to prevent setting limits that are too low and could cause application instability. When a lower bound is configured, any attempt to set a PMEM limit below this threshold will be rejected with an error message. This helps ensure that hosting accounts always have sufficient memory allocated for basic application requirements, preventing performance issues and unexpected application failures. The lower bound is enforced system-wide and applies to all limit-setting operations, whether performed through command-line tools or control panel integrations.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

system-wide

I would format this with bold font.

<div class="notranslate">

```
lvectl --set-pmem-lower-bound 512M

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lvectl

This may be too late to ask, but why did we decide to make it configurable via 2 CLI tools instead of only one? :)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cloudlinux-limits can be used from the CLI, however it is an interface for the UI mainly. It only works with --json flag (for other options as well) and might be useful if in the future we decide to have the ability to set this lower bound from the UI. Initially I implemented it only for lvectl and Roman requested to do the same for cloudlinux-limits


The lower bound value accepts standard memory format notations (e.g., <span class="notranslate">`512M`</span>, <span class="notranslate">`1G`</span>, <span class="notranslate">`2048M`</span>).

The configured PMEM lower bound value is stored in the <span class="notranslate">`/etc/sysconfig/limits_lower_bounds`</span> configuration file.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense to indicate what is the default value out of the box i.e. not configured.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants