{"id":22623,"date":"2026-08-28T13:17:20","date_gmt":"2026-08-28T11:17:20","guid":{"rendered":"https:\/\/www.curiaweb.ch\/?post_type=docs&#038;p=22623"},"modified":"2026-08-28T13:17:21","modified_gmt":"2026-08-28T11:17:21","password":"","slug":"resource-limit-is-reached","status":"publish","type":"docs","link":"https:\/\/www.curiaweb.ch\/en\/hilfe\/webhosting-cpanel\/resource-limit-is-reached\/","title":{"rendered":"Resource Limit Is Reached: Identify and Fix CloudLinux Limits"},"content":{"rendered":"<p class=\"wp-block-paragraph\">If your website temporarily shows the message <strong>Resource Limit Is Reached<\/strong> shows, your hosting account has reached a resource limit managed by CloudLinux.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The message does not automatically mean that the entire hosting server is overloaded. CURIAWEB uses CloudLinux to isolate hosting accounts from each other and provide them with defined resources. If one of these limits is reached, CloudLinux can restrict the further resource usage of the account in question.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this guide we show you how to find out, <strong>which resource limit was reached, when that happened, and which application or task might be responsible for it<\/strong>.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> Do not try to fix the error message by making random changes to PHP, WordPress, or cPanel. First, open CloudLinux Resource Usage and determine which limit was actually reached.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Resource Limit Is Reached<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">CloudLinux manages various resources of a hosting account. Depending on the server configuration, these include, among others:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>CPU performance<\/li>\n\n\n\n<li>physical memory<\/li>\n\n\n\n<li>Input\/Output Performance<\/li>\n\n\n\n<li>concurrent entry processes<\/li>\n\n\n\n<li>Total number of running processes<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If a corresponding limit is reached, further processing can be restricted.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on which resource is affected and which request is currently being processed, this can manifest in different ways.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Possible symptoms include, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Website is responding unusually slowly<\/li>\n\n\n\n<li>individual pages are not loading<\/li>\n\n\n\n<li>Backend is intermittently not responding<\/li>\n\n\n\n<li>PHP processes are taking an unusually long time<\/li>\n\n\n\n<li>Requests fail under load<\/li>\n\n\n\n<li><code>508 Resource Limit Is Reached<\/code> is displayed<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">A 508 error is not automatically a server overload<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An important technical distinction is:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Hosting account reaches CloudLinux limit\n\u2260\nentire hosting server is overloaded<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">CloudLinux uses so-called LVE resource limits to isolate individual hosting accounts from one another.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If your account reaches a limit, this initially affects the resources assigned to your account.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Briefly explained:<\/strong> The error message initially says: \u201eThis hosting account currently needs more of a specific resource than is available within its current limit.\u201c It does not yet say why this is happening.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">1. Note the date and time of the error<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the message only appears sporadically, the exact time is particularly important for the diagnosis.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Take as many notes as possible:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Date\nTime\nAffected domain\nAffected URL\nExecuted action\nVisible error message<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>08\/28\/2026\n02:37 PM\nexample.ch\n\/wp-admin\/\n508 Resource Limit Is Reached<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">From this point on, you can then examine the CloudLinux resources.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2. Open CloudLinux Resource Usage<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Log in to your CURIAWEB cPanel and open:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Metrics \u2192 Resource Usage<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The CloudLinux interface displays the resource usage of your hosting account and can indicate whether resource limits have been reached.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can find a detailed explanation of the individual measured values under <a href=\"\/en\/help\/web-hosting-cpanel\/cloudlinux-resource-usage\/\">Understanding CloudLinux Resource Usage in cPanel<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">3. Select suitable time period<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Select a time period that includes the time of the issue.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the error occurred at 2:37 PM, for example, you are particularly interested in the resource utilization around that time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A limit violation from last evening normally does not explain an error from this afternoon.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">4. Check which limit was reached<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Now comes the most important step: determine, <strong>which resource has actually reached its limit<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the CloudLinux configuration, for example, the following values may be relevant:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Resource<\/th><th>Meaning<\/th><\/tr><\/thead><tbody><tr><td>CPU<\/td><td>available computing power<\/td><\/tr><tr><td>Physical Memory<\/td><td>Memory of the account processes<\/td><\/tr><tr><td>I\/O<\/td><td>Input\/output data rate<\/td><\/tr><tr><td>IOPS<\/td><td>Number of input\/output operations<\/td><\/tr><tr><td>Entry Processes<\/td><td>simultaneously occurring or processed procedures<\/td><\/tr><tr><td>Number of Processes<\/td><td>Total number of running processes of the account<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Which measure makes sense depends largely on, <strong>which of these limits is affected<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">5. Check faults or limit events<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Pay special attention in the CloudLinux evaluation to so-called <strong>Faults<\/strong> or documented limit events.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A high value alone does not automatically mean that the limit has been exceeded or reached.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, the following is important for the diagnosis:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Which limit?\n\u2193\nWhen reached?\n\u2193\nHow often?\n\u2193\nWhat was running at that time?<\/code><\/pre>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Practical Tip:<\/strong> A fault at the exact same time as your website problem is much more meaningful than any random high load several hours beforehand.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">CPU limit reached<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When the CPU limit is reached, your hosting account requires the processing power available to it in full at that time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CloudLinux can limit further CPU usage accordingly. As a result, processes may take longer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical causes can be:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>many dynamic website requests<\/li>\n\n\n\n<li>complex PHP processes<\/li>\n\n\n\n<li>inefficient plugins<\/li>\n\n\n\n<li>extensive database operations<\/li>\n\n\n\n<li>Imports or exports<\/li>\n\n\n\n<li>Cron jobs<\/li>\n\n\n\n<li>Backup or maintenance processes<\/li>\n\n\n\n<li>Bots or an unusually high number of requests<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">CPU limit reached only briefly<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A single short CPU spike does not necessarily have to represent a problem.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, if you are currently running a large import, the CPU usage can temporarily increase significantly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It gets more interesting when:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>the CPU limit is regularly reached<\/li>\n\n\n\n<li>the website is getting slow at the same time<\/li>\n\n\n\n<li>the situation occurs without a manually started task<\/li>\n\n\n\n<li>the behavior is reproducible<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">CPU limit regularly at the same time<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If, for example, the CPU reaches its limit at around the same time every day, check scheduled tasks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical candidates are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cron jobs<\/li>\n\n\n\n<li>Import<\/li>\n\n\n\n<li>Export<\/li>\n\n\n\n<li>Synchronizations<\/li>\n\n\n\n<li>Maintenance tasks<\/li>\n\n\n\n<li>Application backups<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">We explain how to investigate faulty or resource-intensive cron jobs at <a href=\"\/en\/help\/web-hosting-cpanel\/cron-job-is-not-working\/\">Cron job not working: Causes and solutions<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Start multiple cron jobs simultaneously<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When multiple resource-intensive tasks start at the same time, their resource requirements can add up.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>02:00 \u2192 Product import\n02:00 \u2192 Data synchronization\n02:00 \u2192 Export\n02:00 \u2192 Maintenance process<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the applications allow it, it can be useful to stagger such tasks over time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, do not change any cron jobs specified by an application without knowing their function.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Physical Memory Limit reached<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the CloudLinux limit for <strong>Physical Memory<\/strong> is reached, the account's running processes are using too much memory within the available resource limit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical causes may include, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>many simultaneously running PHP processes<\/li>\n\n\n\n<li>memory-intensive imports<\/li>\n\n\n\n<li>Image processing<\/li>\n\n\n\n<li>extensive applications<\/li>\n\n\n\n<li>multiple parallel background processes<\/li>\n\n\n\n<li>faulty or inefficient application code<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Physical Memory is not the PHP Memory Limit<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">These two values are often confused.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The PHP<code>memory_limit<\/code> and the CloudLinux limit for Physical Memory operate on different levels.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Simplified:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>PHP memory_limit\n\u2192 maximum memory limit of a PHP process\n\nCloudLinux Physical Memory\n\u2192 memory consumption of account processes within the LVE<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, if the CloudLinux memory limit is reached, you should <strong>not simply increasing the PHP memory limit<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain how PHP limits work at <a href=\"\/en\/help\/web-hosting-cpanel\/set-php-limits\/\">Set PHP memory limit, upload size, and execution time<\/a>.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Attention:<\/strong> A higher PHP memory limit does not automatically provide your hosting account with more CloudLinux memory.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">\u201eAllowed memory size exhausted\u201c is a different error<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a message like the following appears in the error log:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Allowed memory size of ... bytes exhausted<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">appears, the PHP memory limit of a PHP process has been reached.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is technically to be distinguished from a CloudLinux physical memory limit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the specific error message before changing any settings.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Entry-Process-Limit reached<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Entry Processes<\/strong> or rather <code>EP<\/code> describe simplified processes entering or being processed in the CloudLinux LVE environment simultaneously.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The EP limit can become particularly relevant when there are many dynamic requests to be processed simultaneously.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If this limit is reached, additional requests cannot be processed normally.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this context, in particular, a:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>508 Resource Limit Is Reached<\/code><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">occur.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Entry processes are not your visitor count<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An EP limit of, for example, a specific value does not mean that only a corresponding number of people can visit your website at the same time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Visitors and entry processes are different metrics.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Among other things, the crucial factor is how long dynamic requests are processed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Simplified:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>fast request\n\u2192 process completes quickly\n\u2192 resource becomes available again\n\nslow request\n\u2192 process remains active longer\n\u2192 more concurrent processes can accumulate<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, a slow application can strain the EP limit more heavily even with comparatively moderate traffic.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What can cause many entry processes?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Possible causes include, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>many simultaneous dynamic requests<\/li>\n\n\n\n<li>slow PHP processing<\/li>\n\n\n\n<li>slow database operations<\/li>\n\n\n\n<li>uncached dynamic pages<\/li>\n\n\n\n<li>Bots or automated access<\/li>\n\n\n\n<li>long-running application processes<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, with WordPress or WooCommerce, not only the number of visitors is relevant, but also how efficiently individual requests are processed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Number-of-Processes-Limit reached<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">CloudLinux can additionally limit the total number of processes for a hosting account.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This value is often used as <code>NPROC<\/code> or rather <strong>Number of Processes<\/strong> referred to as.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Unlike entry processes, NPROC does not only consider web processes occurring simultaneously.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Other running processes of the account may also be relevant.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Examine many processes<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the process limit is regularly reached, check in particular:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>concurrently running cron jobs<\/li>\n\n\n\n<li>long-running PHP processes<\/li>\n\n\n\n<li>Background tasks<\/li>\n\n\n\n<li>Import and export processes<\/li>\n\n\n\n<li>multiple applications within the same hosting account<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Even an old test installation can run background tasks, even though it is no longer actively used.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">I\/O limit reached<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The I\/O limit affects the speed at which processes can read or write data.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the available I\/O performance is fully utilized, dependent processes may slow down.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical triggers can be:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>large file operations<\/li>\n\n\n\n<li>Backups<\/li>\n\n\n\n<li>Extracting large archives<\/li>\n\n\n\n<li>extensive imports<\/li>\n\n\n\n<li>many write operations<\/li>\n\n\n\n<li>Cache generation<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Distinguish between I\/O limit and full storage space<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An I\/O limit does not mean that your hosting storage is full.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>I\/O limit\n\u2192 Speed of file operations limited\n\nStorage space full\n\u2192 No or insufficient space for additional data<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You can check the actual memory consumption under <a href=\"\/en\/help\/web-hosting-cpanel\/check-storage-space-and-bandwidth\/\">Check disk space and bandwidth in cPanel<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">IOPS limit reached<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If additionally in your CloudLinux evaluation <strong>IOPS<\/strong> displayed, this value describes the number of input\/output operations per second.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Many small file operations can therefore consume an IOPS limit, even if the total amount of data transferred does not appear exceptionally large.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Which resource was reached?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The following overview helps with the initial classification:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Limit<\/th><th>Typical initial inspection points<\/th><\/tr><\/thead><tbody><tr><td>CPU<\/td><td>PHP, Plugins, Cronjobs, Imports, Traffic<\/td><\/tr><tr><td>Physical Memory<\/td><td>memory-intensive and parallel processes<\/td><\/tr><tr><td>Entry Processes<\/td><td>simultaneous or slow dynamic queries<\/td><\/tr><tr><td>Number of Processes<\/td><td>Background processes, cron jobs, parallel tasks<\/td><\/tr><tr><td>I\/O<\/td><td>Backups, file operations, archives, imports<\/td><\/tr><tr><td>IOPS<\/td><td>very many individual file operations<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Check what was running at the time of the error<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After identifying the affected limit, you should find out which activity took place at the same time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Was an import performed?<\/li>\n\n\n\n<li>Did a cron job run?<\/li>\n\n\n\n<li>Was a backup created?<\/li>\n\n\n\n<li>Were there an unusual number of visitors?<\/li>\n\n\n\n<li>Were bots active?<\/li>\n\n\n\n<li>Has WordPress just been updated?<\/li>\n\n\n\n<li>Was a synchronization running?<\/li>\n\n\n\n<li>Was a large archive processed?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">First, this connection between <strong>Limit + Time + Activity<\/strong> leads to a reliable diagnosis.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">7. Check cPanel Error Log at the same time<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the website simultaneously shows PHP or server errors, also open:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Measured values \u2192 Errors<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check there whether a matching error message was logged at the same time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain how to read these entries at <a href=\"\/en\/help\/web-hosting-cpanel\/read-cpanel-error-log\/\">Read cPanel Error Log and find website errors<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">CloudLinux limits and PHP errors can occur together<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A resource issue and an application error are not mutually exclusive.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a faulty process can:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>run unusually long\n        \u2193\nconsume a lot of CPU or memory\n        \u2193\nreach CloudLinux limit<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">In this case, the resource limit is a consequence of the actual application problem.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Investigate WordPress as a cause<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In WordPress, plugins, themes, and background tasks can have a significant impact on resource consumption.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the problem started immediately after a change, check in particular:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>newly installed plugin<\/li>\n\n\n\n<li>Plugin update<\/li>\n\n\n\n<li>Theme Update<\/li>\n\n\n\n<li>WordPress update<\/li>\n\n\n\n<li>new import function<\/li>\n\n\n\n<li>Backup plugin<\/li>\n\n\n\n<li>Security or statistics plugin<\/li>\n\n\n\n<li>custom code<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">We explain how to systematically investigate plugin and theme conflicts at <a href=\"\/en\/help\/wordpress\/wordpress-plugin-theme-conflicts\/\">Identify and resolve WordPress plugin and theme conflicts<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Consider WP-Cron and background tasks<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress uses its own scheduled events for various background tasks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Plugins can use this to, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Process emails<\/li>\n\n\n\n<li>Synchronize data<\/li>\n\n\n\n<li>Fetch feeds<\/li>\n\n\n\n<li>Create reports<\/li>\n\n\n\n<li>Clean data<\/li>\n\n\n\n<li>Run updates or other maintenance tasks<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, a resource-intensive background task can occur even when you are not currently doing anything in the WordPress backend yourself.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Give special consideration to WooCommerce<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WooCommerce processes numerous dynamic operations and background tasks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This may include, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cart<\/li>\n\n\n\n<li>Checkout<\/li>\n\n\n\n<li>Customer account<\/li>\n\n\n\n<li>Orders<\/li>\n\n\n\n<li>Product imports<\/li>\n\n\n\n<li>Synchronizations<\/li>\n\n\n\n<li>scheduled actions of extensions<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, in an online shop, you should check precisely which task was being executed at the time of the resource event.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Consider WordPress Action Scheduler<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WooCommerce and numerous WordPress extensions use the Action Scheduler for background tasks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If a large number of pending or failing tasks have accumulated, this can contribute to recurring background activity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If your resource problem occurs regularly, the queue of scheduled tasks within the application in question can therefore also be relevant.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Check for bots and crawlers as a cause<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Automated requests can cause significant resource consumption, especially when many dynamic URLs are accessed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A bot doesn't necessarily have to be a malicious attacker.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Also:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Search engines<\/li>\n\n\n\n<li>SEO crawler<\/li>\n\n\n\n<li>Monitoring services<\/li>\n\n\n\n<li>Price or content crawler<\/li>\n\n\n\n<li>automated scanners<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">can generate numerous requests.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Compare access statistics with the resource event<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a limit coincides with unusually high traffic, you can additionally use the cPanel tools under <strong>Measurements<\/strong> use.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the evaluation, visitor, bandwidth, raw access, and statistical data, among others, are available there.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This allows you to better assess whether a peak load coincides with increased data traffic.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Traffic is not automatically the cause<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A resource limit during high traffic does not necessarily mean that the visitor count is exclusively the problem.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If individual dynamic pages are processed very slowly, even moderate traffic can lead to many simultaneously running processes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, the efficiency of the application should always be examined as well.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Check caching<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For dynamic websites, appropriate caching can significantly reduce the number of PHP and database operations for recurring page views.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CURIAWEB provides AccelerateWP, a WordPress-oriented optimization solution.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can find more information at <a href=\"\/en\/help\/web-hosting-cpanel\/acceleratewp-erklaert\/\">AccelerateWP in cPanel explained<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Do not install multiple cache systems on top of each other<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When a resource limit is reached, a common erroneous reaction is to install multiple performance plugins at the same time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This can:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>cause conflicts<\/li>\n\n\n\n<li>Manage cache contents inconsistently<\/li>\n\n\n\n<li>complicate troubleshooting<\/li>\n\n\n\n<li>impair dynamic functions<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, use controlled optimization and check the result after each change.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Caching doesn't help with every cause<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Caching can be particularly helpful with repeated frontend calls.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, it does not automatically solve, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>faulty cron jobs<\/li>\n\n\n\n<li>resource-intensive imports<\/li>\n\n\n\n<li>Backend processes<\/li>\n\n\n\n<li>certain WooCommerce tasks<\/li>\n\n\n\n<li>faulty application code<\/li>\n\n\n\n<li>unusually large database operations<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The cause must therefore continue to be identified.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Check PHP version<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A suitable PHP version supported by the application can be relevant for performance and stability.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At CURIAWEB, you generally manage the PHP version of your domain via the <a href=\"\/en\/help\/web-hosting-cpanel\/change-php-version\/\">MultiPHP Manager<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, do not blindly change the PHP version just because of a resource error.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check first which versions your website, plugins, and themes support.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Check PHP extensions<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If error messages regarding missing PHP functions or classes occur at the same time, a required PHP extension may additionally be relevant.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain the procedure under <a href=\"\/en\/help\/web-hosting-cpanel\/enable-php-extensions\/\">Enabling and Managing PHP Extensions in cPanel<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Do not confuse PHP limits with CloudLinux limits<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">PHP settings such as:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>memory_limit\nmax_execution_time\nupload_max_filesize\npost_max_size<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">are no CloudLinux limits.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, if CloudLinux reports a CPU or Entry Process limit, this issue will not be resolved by you <code>upload_max_filesize<\/code> or <code>memory_limit<\/code> increase.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Check storage space<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A full hosting storage is also not a CloudLinux CPU limit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you experience writing, updating, or email problems at the same time, you should also check the available disk space.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can find the procedure under <a href=\"\/en\/help\/web-hosting-cpanel\/check-storage-space-and-bandwidth\/\">Check disk space and bandwidth in cPanel<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Consider multiple websites in the account<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When multiple websites are operated within the same hosting account, they share the resources of that account.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This means:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Website A\nWebsite B\nWebsite C\nCron jobs\nBackground processes\n        \u2193\nShared account resources<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, the resource problem does not necessarily have to be caused by the domain where you first saw the error message.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Don't forget old test installations<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An old WordPress test site can still be accessed by bots and execute background tasks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, even installations that are no longer actively used can consume resources.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check with recurring problems which applications are actually still present in the hosting account.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Staging websites can also execute processes<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Technically speaking, a staging copy is just another website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If WordPress, plugins, cron jobs, or other background processes are active there, they can also use resources.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, also consider test and staging environments.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Critically review backup plugins<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the configuration, WordPress backup plugins can generate large amounts of data:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>read<\/li>\n\n\n\n<li>compress<\/li>\n\n\n\n<li>write<\/li>\n\n\n\n<li>transfer<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This can affect CPU, I\/O, memory, and process runtimes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If resource issues occur regularly during a plugin backup, you should check its schedule and configuration.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Gro\u00dfe Archive k\u00f6nnen mehrere Ressourcen gleichzeitig beanspruchen<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Das Erstellen oder Entpacken eines gro\u00dfen ZIP-Archivs kann beispielsweise gleichzeitig:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>CPU<\/li>\n\n\n\n<li>I\/O<\/li>\n\n\n\n<li>IOPS<\/li>\n\n\n\n<li>RAM<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">beanspruchen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Betrachte deshalb nicht nur einen einzelnen Messwert, wenn mehrere Ressourcen zum gleichen Zeitpunkt auff\u00e4llig sind.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Importe kontrolliert durchf\u00fchren<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn ein gro\u00dfer Import regelm\u00e4\u00dfig Ressourcenlimits erreicht, pr\u00fcfe, ob die verwendete Anwendung kleinere Verarbeitungspakete oder eine andere Batch-Gr\u00f6\u00dfe unterst\u00fctzt.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bei einem Produktimport kann es beispielsweise effizienter sein, kontrollierte Teilmengen zu verarbeiten, statt eine extrem gro\u00dfe Datenmenge in einem einzigen Vorgang zu erzwingen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Welche Einstellung sinnvoll ist, h\u00e4ngt von der jeweiligen Anwendung ab.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Datenbankprobleme ber\u00fccksichtigen<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Langsame oder sehr aufwendige Datenbankoperationen k\u00f6nnen dazu f\u00fchren, dass PHP-Prozesse l\u00e4nger aktiv bleiben.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dadurch k\u00f6nnen sich unter Last weitere Prozesse ansammeln.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ein Ressourcenlimit kann deshalb auch ein Symptom einer ineffizienten Anwendung oder Datenbankabfrage sein.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Fehlerhafte Prozesse statt h\u00f6herem Limit<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn ein einzelner fehlerhafter Prozess unn\u00f6tig Ressourcen verbraucht, w\u00e4re eine reine Erh\u00f6hung des Limits keine nachhaltige L\u00f6sung.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Plugin erzeugt Endlosschleife\n        \u2193\nCPU dauerhaft hoch\n        \u2193\nCPU-Limit erreicht<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Die eigentliche L\u00f6sung besteht dann darin, den fehlerhaften Prozess zu korrigieren \u2013 nicht lediglich darin, ihm mehr CPU zur Verf\u00fcgung zu stellen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Wann mehr Ressourcen tats\u00e4chlich sinnvoll sein k\u00f6nnen<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Nicht jedes Ressourcenlimit ist auf einen Fehler zur\u00fcckzuf\u00fchren.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Eine technisch saubere und gut optimierte Website kann aufgrund ihres tats\u00e4chlichen Nutzungsumfangs mehr Ressourcen ben\u00f6tigen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Das kann beispielsweise bei:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>stark gewachsenem Traffic<\/li>\n\n\n\n<li>umfangreichen Onlineshops<\/li>\n\n\n\n<li>vielen gleichzeitigen dynamischen Zugriffen<\/li>\n\n\n\n<li>ressourcenintensiven Webanwendungen<\/li>\n\n\n\n<li>regelm\u00e4\u00dfig gro\u00dfen Verarbeitungsaufgaben<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">der Fall sein.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bevor du zu diesem Schluss kommst, sollte jedoch gepr\u00fcft werden, ob die vorhandenen Ressourcen effizient genutzt werden.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Important:<\/strong> \u201eMehr Ressourcen\u201c und \u201eWebsite optimieren\u201c sind keine Gegens\u00e4tze. Eine wachsende Anwendung kann beides ben\u00f6tigen: effiziente Software und eine zum tats\u00e4chlichen Bedarf passende Hosting-Ausstattung.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Wann Optimierung sinnvoller ist<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Eine Optimierung sollte insbesondere dann im Vordergrund stehen, wenn:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ein einzelnes Plugin extrem viel Last verursacht<\/li>\n\n\n\n<li>Fehler oder Endlosschleifen auftreten<\/li>\n\n\n\n<li>unn\u00f6tige Cronjobs parallel laufen<\/li>\n\n\n\n<li>Bot-Traffic ungew\u00f6hnlich hoch ist<\/li>\n\n\n\n<li>Caching fehlt oder falsch konfiguriert ist<\/li>\n\n\n\n<li>alte Installationen unn\u00f6tig Prozesse ausf\u00fchren<\/li>\n\n\n\n<li>eine Datenbankoperation ineffizient arbeitet<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Wann zus\u00e4tzliche Ressourcen gepr\u00fcft werden sollten<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Zus\u00e4tzliche Ressourcen k\u00f6nnen dagegen sinnvoll sein, wenn:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>die Website technisch sauber funktioniert<\/li>\n\n\n\n<li>keine offensichtlichen Fehlerprozesse vorhanden sind<\/li>\n\n\n\n<li>die Anwendung bereits sinnvoll optimiert ist<\/li>\n\n\n\n<li>die Limits aufgrund legitimer Nutzung regelm\u00e4\u00dfig erreicht werden<\/li>\n\n\n\n<li>der tats\u00e4chliche Ressourcenbedarf dauerhaft gestiegen ist<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Die Entscheidung sollte anhand der gemessenen Ressourcen und der tats\u00e4chlichen Anwendung getroffen werden \u2013 nicht allein anhand einer einzelnen Fehlermeldung.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Problem nur einmal aufgetreten<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn ein Ressourcenlimit einmalig w\u00e4hrend einer au\u00dfergew\u00f6hnlichen Aufgabe erreicht wurde und danach nicht wieder auftritt, besteht nicht automatisch dauerhafter Handlungsbedarf.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>one-time large import<\/li>\n\n\n\n<li>Migration<\/li>\n\n\n\n<li>Erstellung eines gro\u00dfen Archivs<\/li>\n\n\n\n<li>au\u00dfergew\u00f6hnliche Traffic-Spitze<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Dokumentiere das Ereignis und beobachte, ob es erneut auftritt.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Problem tritt t\u00e4glich auf<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn dasselbe Limit t\u00e4glich ungef\u00e4hr zur gleichen Zeit erreicht wird, spricht dies h\u00e4ufig f\u00fcr einen wiederkehrenden Prozess.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Cronjobs\nWordPress-Hintergrundaufgaben\nWooCommerce Scheduled Actions\nBackups\nSynchronisationen\nImporte\nExporte<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Der wiederkehrende Zeitpunkt ist dabei ein besonders wertvoller Hinweis.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Problem tritt nur bei vielen Besuchern auf<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn Ressourcenlimits ausschlie\u00dflich bei erh\u00f6htem Traffic auftreten, solltest du untersuchen:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>welches Limit erreicht wird<\/li>\n\n\n\n<li>welche URLs besonders h\u00e4ufig aufgerufen werden<\/li>\n\n\n\n<li>ob diese Seiten dynamisch verarbeitet werden<\/li>\n\n\n\n<li>whether caching is used sensibly<\/li>\n\n\n\n<li>ob Bots einen Teil der Last verursachen<\/li>\n\n\n\n<li>wie schnell einzelne Anfragen verarbeitet werden<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Nur die Besucherzahl zu betrachten reicht f\u00fcr eine technische Diagnose nicht aus.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Problem tritt nur im WordPress-Backend auf<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Das WordPress-Backend enth\u00e4lt viele Bereiche, die nicht wie \u00f6ffentliche Seiten vollst\u00e4ndig zwischengespeichert werden k\u00f6nnen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn Ressourcenprobleme nur bei bestimmten Administrationsaufgaben auftreten, solltest du genau diese Aktion untersuchen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Examples:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Produktimport<\/li>\n\n\n\n<li>Berichterstellung<\/li>\n\n\n\n<li>Massenbearbeitung<\/li>\n\n\n\n<li>Plugin-Scan<\/li>\n\n\n\n<li>Datenbankbereinigung<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Problem tritt nur beim Checkout auf<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bei WooCommerce ist der Checkout ein dynamischer Vorgang.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn Ressourcenprobleme ausschlie\u00dflich dort auftreten, sollte nicht einfach die gesamte Website gecacht werden.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Untersuche stattdessen die am Checkout beteiligten Plugins, Zahlungsdienste, Datenbankoperationen und externen Verbindungen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Problem nach Plugin-Update<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn die Ressourcennutzung unmittelbar nach einem Plugin-Update deutlich ansteigt, ist der zeitliche Zusammenhang ein wichtiger Hinweis.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Changelog und Systemanforderungen<\/li>\n\n\n\n<li>PHP compatibility<\/li>\n\n\n\n<li>neue Hintergrundfunktionen<\/li>\n\n\n\n<li>Fehlermeldungen<\/li>\n\n\n\n<li>Konflikte mit anderen Erweiterungen<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">\u00c4ndere nicht gleichzeitig mehrere andere Komponenten, da dies die Diagnose erschwert.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Problem nach PHP-Wechsel<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn das Problem unmittelbar nach einer \u00c4nderung der PHP-Version auftritt, kontrolliere:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Kompatibilit\u00e4t der Anwendung<\/li>\n\n\n\n<li>Plugins and Themes<\/li>\n\n\n\n<li>required PHP extensions<\/li>\n\n\n\n<li>Error Log<\/li>\n\n\n\n<li>Ressourcenwerte vor und nach dem Wechsel<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Ein kontrollierter Wechsel auf die zuvor funktionierende PHP-Version kann ein sinnvoller Diagnoseschritt sein, sofern diese Version weiterhin unterst\u00fctzt und f\u00fcr die Anwendung geeignet ist.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Problem nach Migration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn eine migrierte Website auf dem neuen Hosting ungew\u00f6hnlich viele Ressourcen ben\u00f6tigt, pr\u00fcfe unter anderem:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PHP version<\/li>\n\n\n\n<li>PHP extensions<\/li>\n\n\n\n<li>Cron jobs<\/li>\n\n\n\n<li>Cache configuration<\/li>\n\n\n\n<li>alte absolute Pfade<\/li>\n\n\n\n<li>Application error<\/li>\n\n\n\n<li>mehrfach vorhandene Testinstallationen<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Eine Migration kann Unterschiede in der Server- oder Anwendungskonfiguration sichtbar machen, die vorher nicht aufgefallen sind.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Nicht alle Ma\u00dfnahmen gleichzeitig durchf\u00fchren<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you simultaneously:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>PHP wechselst\nPlugins deaktivierst\nCache neu konfigurierst\nCronjobs \u00e4nderst\nDatenbank optimierst<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">und das Problem anschlie\u00dfend verschwindet, wei\u00dft du nicht, welche \u00c4nderung tats\u00e4chlich geholfen hat.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Gehe deshalb kontrolliert vor:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>eine Hypothese\n        \u2193\neine gezielte \u00c4nderung\n        \u2193\nerneut testen\n        \u2193\nRessourcen vergleichen<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Ressourcennutzung nach einer \u00c4nderung kontrollieren<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Nach einer Optimierung solltest du nicht nur pr\u00fcfen, ob die Fehlermeldung verschwunden ist.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Kontrolliere auch, ob sich die zugrunde liegenden Ressourcenwerte verbessert haben.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Vorher:\nEP-Limit t\u00e4glich mehrfach erreicht\n\n\u00c4nderung:\nlangsamen Hintergrundprozess korrigiert\n\nNachher:\nkeine EP-Faults im vergleichbaren Zeitraum<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Damit erh\u00e4ltst du einen wesentlich besseren Nachweis, dass die Ma\u00dfnahme tats\u00e4chlich wirksam war.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Resource Limit Is Reached systematisch diagnostizieren<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Notiere Datum, Uhrzeit und betroffene URL.<\/li>\n\n\n\n<li>Open <strong>Metrics \u2192 Resource Usage<\/strong>.<\/li>\n\n\n\n<li>W\u00e4hle den passenden Zeitraum.<\/li>\n\n\n\n<li>Pr\u00fcfe, welches Limit erreicht wurde.<\/li>\n\n\n\n<li>Kontrolliere Faults beziehungsweise Limit-Ereignisse.<\/li>\n\n\n\n<li>Vergleiche deren Zeitpunkt mit dem Website-Problem.<\/li>\n\n\n\n<li>Pr\u00fcfe, welche Prozesse oder Aufgaben zu diesem Zeitpunkt liefen.<\/li>\n\n\n\n<li>Kontrolliere Cronjobs und Hintergrundaufgaben.<\/li>\n\n\n\n<li>Pr\u00fcfe bei WordPress Plugins, Themes und geplante Aktionen.<\/li>\n\n\n\n<li>Kontrolliere bei Website-Fehlern zus\u00e4tzlich das Error Log.<\/li>\n\n\n\n<li>Pr\u00fcfe ungew\u00f6hnlichen Traffic beziehungsweise Bots.<\/li>\n\n\n\n<li>Change only one possible cause at a time.<\/li>\n\n\n\n<li>Teste anschlie\u00dfend erneut.<\/li>\n\n\n\n<li>Vergleiche die CloudLinux-Werte vor und nach der \u00c4nderung.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Was du nicht tun solltest<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Avoid in particular:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PHP Memory Limit ohne Diagnose extrem erh\u00f6hen<\/li>\n\n\n\n<li>mehrere Cache-Plugins gleichzeitig installieren<\/li>\n\n\n\n<li>Switch PHP versions randomly<\/li>\n\n\n\n<li>Cronjobs ohne Kenntnis ihrer Funktion l\u00f6schen<\/li>\n\n\n\n<li>Plugins und Themes gleichzeitig massenweise deaktivieren<\/li>\n\n\n\n<li>gro\u00dfe Dateien auf Verdacht l\u00f6schen<\/li>\n\n\n\n<li>jeden einmaligen Peak als dauerhaftes Hosting-Problem interpretieren<\/li>\n<\/ul>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\"><strong>Basic rule:<\/strong> Ein Ressourcenfehler wird nicht zuverl\u00e4ssig behoben, indem du m\u00f6glichst viele Einstellungen \u00e4nderst. Du musst zuerst herausfinden, welches Limit erreicht wird und welcher Prozess zu diesem Zeitpunkt Ressourcen ben\u00f6tigt.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Website zeigt keinen 508-Fehler, ist aber langsam<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ein Hosting-Account kann Ressourcenlimits erreichen, ohne dass jeder Besucher zwingend eine sichtbare 508-Seite erh\u00e4lt.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CPU- oder I\/O-Begrenzungen k\u00f6nnen sich beispielsweise zun\u00e4chst durch langsamere Verarbeitung bemerkbar machen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn eine Website sporadisch langsam ist, solltest du deshalb auch ohne sichtbaren 508-Fehler die CloudLinux-Ressourcennutzung zum betreffenden Zeitpunkt pr\u00fcfen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Keine CloudLinux-Limits erreicht<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn CloudLinux im relevanten Zeitraum keine passenden Limit-Ereignisse zeigt, solltest du die Fehlersuche auf andere Ebenen erweitern.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Possible causes include, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PHP error<\/li>\n\n\n\n<li>Datenbankprobleme<\/li>\n\n\n\n<li>external services<\/li>\n\n\n\n<li>DNS<\/li>\n\n\n\n<li>SSL<\/li>\n\n\n\n<li>Plugin- oder Theme-Fehler<\/li>\n\n\n\n<li>Browser- beziehungsweise Frontend-Probleme<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Versuche nicht, ein Ressourcenproblem zu beheben, wenn die Messwerte daf\u00fcr keine Hinweise liefern.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">When should you contact CURIAWEB support?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Wenn dein Hosting-Account regelm\u00e4\u00dfig CloudLinux-Limits erreicht und du die verursachende Anwendung oder Aufgabe nicht eindeutig identifizieren kannst, dokumentiere das Problem m\u00f6glichst genau.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Particularly helpful are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>affected domain<\/li>\n\n\n\n<li>betroffene URL oder Funktion<\/li>\n\n\n\n<li>Date and exact time<\/li>\n\n\n\n<li>visible error message<\/li>\n\n\n\n<li>betroffenes CloudLinux-Limit<\/li>\n\n\n\n<li>angezeigte Faults beziehungsweise Limit-Ereignisse<\/li>\n\n\n\n<li>H\u00e4ufigkeit des Problems<\/li>\n\n\n\n<li>recent changes<\/li>\n\n\n\n<li>running cron jobs, imports, or background tasks<\/li>\n\n\n\n<li>relevant error log entries<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Mit diesen Angaben l\u00e4sst sich wesentlich schneller beurteilen, ob ein fehlerhafter Prozess, eine Optimierungsm\u00f6glichkeit oder ein dauerhaft h\u00f6herer Ressourcenbedarf vorliegt.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Summary<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Die Meldung <strong>Resource Limit Is Reached<\/strong> bedeutet, dass dein Hosting-Account ein von CloudLinux verwaltetes Ressourcenlimit erreicht hat. Sie bedeutet nicht automatisch, dass der gesamte Hosting-Server \u00fcberlastet ist.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00d6ffne zuerst <strong>Metrics \u2192 Resource Usage<\/strong> und pr\u00fcfe den Zeitraum, in dem das Problem aufgetreten ist. Entscheidend ist anschlie\u00dfend, welches Limit tats\u00e4chlich erreicht wurde.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CPU, Physical Memory, Entry Processes, Number of Processes, I\/O und IOPS beschreiben unterschiedliche Ressourcen. Entsprechend unterscheiden sich auch die m\u00f6glichen Ursachen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ein CPU-Limit kann beispielsweise durch aufwendige PHP-Prozesse, Cronjobs oder hohe dynamische Last entstehen. Ein EP-Limit deutet dagegen auf zu viele gleichzeitig verarbeitete eingehende Prozesse hin. Physical Memory wiederum darf nicht mit dem PHP-<code>memory_limit<\/code> verwechselt werden.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Vergleiche Limit-Ereignisse immer mit dem genauen Zeitpunkt des Website-Problems. Pr\u00fcfe anschlie\u00dfend Cronjobs, WordPress-Hintergrundaufgaben, Plugins, Importe, Backups, Traffic und Error Logs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ein Ressourcenlimit ist au\u00dferdem nicht automatisch ein Beweis daf\u00fcr, dass dein Hosting-Paket grunds\u00e4tzlich zu klein ist. Fehlerhafter Code, ung\u00fcnstige Cronjobs oder fehlende Optimierung k\u00f6nnen unn\u00f6tige Last verursachen. Umgekehrt kann eine technisch saubere, stark gewachsene Website tats\u00e4chlich dauerhaft mehr Ressourcen ben\u00f6tigen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The most important rule is: <strong>Erst das betroffene Limit identifizieren, dann die verursachende Aktivit\u00e4t finden und erst danach entscheiden, ob optimiert, korrigiert oder tats\u00e4chlich mehr Ressourcen ben\u00f6tigt werden.<\/strong><\/p>","protected":false},"excerpt":{"rendered":"<p>Wenn deine Website zeitweise die Meldung Resource Limit Is Reached zeigt, hat dein Hosting-Account ein von CloudLinux verwaltetes Ressourcenlimit erreicht. Die Meldung bedeutet nicht automatisch, dass der gesamte Hosting-Server \u00fcberlastet ist. CURIAWEB verwendet CloudLinux, um Hosting-Accounts voneinander zu isolieren und ihnen definierte Ressourcen zur Verf\u00fcgung zu stellen. Wird eine dieser Grenzen erreicht, kann CloudLinux die [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_joinchat":[],"footnotes":""},"doc_category":[78],"doc_tag":[],"class_list":["post-22623","docs","type-docs","status-publish","hentry","doc_category-webhosting-cpanel"],"year_month":"2026-09","word_count":3988,"total_views":"4","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"name":"Silvio Mazenauer","author_nicename":"admin-curia","author_url":"https:\/\/www.curiaweb.ch\/en\/author\/admin-curia\/"},"doc_category_info":[{"term_name":"Webhosting &amp; cPanel","term_url":"https:\/\/www.curiaweb.ch\/en\/hilfe-kategorie\/webhosting-cpanel\/"}],"doc_tag_info":[],"knowledge_base_info":[],"knowledge_base_slug":[],"_links":{"self":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22623","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/comments?post=22623"}],"version-history":[{"count":1,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22623\/revisions"}],"predecessor-version":[{"id":22625,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22623\/revisions\/22625"}],"wp:attachment":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/media?parent=22623"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_category?post=22623"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_tag?post=22623"}],"curies":[{"name":"WP","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}