fdbd899766
- Remaining Developer Guides and Upgrading - SilverStripe in a namespace or api has not been change - To keep PRs easier no formatting was changed Update merge conflics with two files Update Silverstripe Ltd, Silverstripe Cloud and Silverstripe CMS Silverstripe CMS Ltd > Silverstripe Ltd Silverstripe CMS Platform > Silverstripe Cloud Silverstripe CMS Framework > Silverstripe CMS Resolve merge conflict Remove Framework from Silverstripe CMS Framework - 3 files Change SilverStripe CMS to Silverstripe CMS
1.3 KiB
| title | summary | icon |
|---|---|---|
| Resource Usage | Manage Silverstripe CMS's memory footprint and CPU usage. | tachometer-alt |
Resource Usage
Silverstripe CMS tries to keep its resource usage within the documented limits (see the server requirements).
These limits are defined through memory_limit and max_execution_time in the PHP configuration. They can be
overwritten through ini_set(), unless PHP is running with the Suhoshin Patches
or in "safe mode".
[alert] Most shared hosting providers will have maximum values that can't be altered. [/alert]
For certain tasks like synchronizing a large assets/ folder with all file and folder entries in the database, more
resources are required temporarily. In general, we recommend running resource intensive tasks through the
command line, where configuration defaults for these settings are higher or even unlimited.
[info]
Silverstripe CMS can request more resources through Environment::increaseMemoryLimitTo() and
Environment::increaseTimeLimitTo() functions.
[/info]
use SilverStripe\Core\Environment;
public function myBigFunction()
{
Environment::increaseTimeLimitTo(400);
}