Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Apiscp php memory limit

Does anyone know how to increase the PHP memory limit in ApisCP? I edited all the PHP INI files, but nothing worked. I even sought help from ChatGPT, but still no success. All other PHP settings were updated using PHP INI, but the PHP memory limit didn't change. I believe there might be some other settings involved. Any suggestions?

Comments

  • plumbergplumberg Veteran, Megathread Squad

    Did you try apiscp support?

  • plumbergplumberg Veteran, Megathread Squad

    Or their documentation?

  • Yes, I contacted support, and they replied quite quickly. They informed me that the PHP memory limit cannot be changed from the php.ini file; instead, it must be changed via an SSH command. Here is the link they provided: PHP-FPM Policy Map.
    https://docs.apiscp.com/admin/PHP-FPM/#policy-map-api

    admins pls close this thread its resolved by ApisCP support

  • nemnem Member, Host Rep

    It's controlled by a policy map or overriding the configuration administratively. CLI is the quickest way to apply it per-site.

    384 MB is a good balance between a site DoS'ing itself on really crummy code and giving enough headroom for one-off scripts. Note, in these situations, cgroup,memory is still the upper ceiling on the amount of memory a site can consume in full. Ideally, with memory_limit < cgroup,memory your site will continue to operate even if a script is behaving badly.

  • @nem said:
    It's controlled by a policy map or overriding the configuration administratively. CLI is the quickest way to apply it per-site.

    384 MB is a good balance between a site DoS'ing itself on really crummy code and giving enough headroom for one-off scripts. Note, in these situations, cgroup,memory is still the upper ceiling on the amount of memory a site can consume in full. Ideally, with memory_limit < cgroup,memory your site will continue to operate even if a script is behaving badly.

    Yes, you are right, but the WordPress website I plan to host on ApisCP has more than 200,000 posts, and it slows down with less than 2 GB of memory. I'm already using CyberPanel, and ApisCP has impressed me a lot. There's a bit of a learning curve, but I can see that it's one of the most secure all-in-one solutions, which is why I'm testing ApisCP.

    Thanked by 1nem
Sign In or Register to comment.