{"id":22620,"date":"2026-08-28T13:14:37","date_gmt":"2026-08-28T11:14:37","guid":{"rendered":"https:\/\/www.curiaweb.ch\/?post_type=docs&#038;p=22620"},"modified":"2026-08-28T13:14:37","modified_gmt":"2026-08-28T11:14:37","password":"","slug":"cloudlinux-resource-usage","status":"publish","type":"docs","link":"https:\/\/www.curiaweb.ch\/en\/hilfe\/webhosting-cpanel\/cloudlinux-ressourcennutzung\/","title":{"rendered":"Understanding CloudLinux Resource Usage in cPanel"},"content":{"rendered":"<p class=\"wp-block-paragraph\">If a website is temporarily slow, processes abort, or errors only occur under load, you should check the available hosting resources in addition to PHP errors and disk space.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CURIAWEB uses CloudLinux to isolate hosting accounts from one another and allocate resources in a controlled manner. In cPanel, under <strong>Metrics \u2192 Resource Usage<\/strong> understand whether your account has reached resource limits and which resources were particularly heavily used at a specific time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this guide, we will show you how to open the CloudLinux resource usage, correctly classify the most important metrics, and distinguish between a brief traffic spike and an actual resource issue.<\/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> A high measurement or a single peak load does not automatically mean that something is wrong with your website. What matters is whether a limit is actually reached, how often that happens, and whether the timing coincides with a visible problem on the website.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">What does CloudLinux do?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">On a shared hosting system, multiple hosting accounts use the same physical server infrastructure.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CloudLinux ensures, among other things, that the resources of individual accounts are isolated from one another. This prevents, for example, a heavily loaded website from consuming unlimited resources on the entire server.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a single hosting account, various resources can be considered and limited separately.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the server configuration, this includes in particular:<\/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>simultaneous incoming processes<\/li>\n\n\n\n<li>Total number of processes<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The CloudLinux display helps you identify, <strong>which resource was claimed at what time<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">CloudLinux resources are not your storage space<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">One of the most important distinctions is that between hosting storage and running system resources.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Area<\/th><th>Meaning<\/th><\/tr><\/thead><tbody><tr><td>Storage space<\/td><td>Storage space for files, emails, databases, and other stored data<\/td><\/tr><tr><td>bandwidth<\/td><td>transmitted data<\/td><\/tr><tr><td>Physical Memory<\/td><td>RAM used by running processes<\/td><\/tr><tr><td>CPU<\/td><td>Processing power for running processes<\/td><\/tr><tr><td>I\/O<\/td><td>Input\/output data rate<\/td><\/tr><tr><td>Entry Processes<\/td><td>simultaneously processed incoming processes within the CloudLinux LVE context<\/td><\/tr><tr><td>Processes<\/td><td>Number of running processes of the account<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">If you want to know which files or emails are taking up your hosting storage, use instead <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\">1. Open Resource Usage in cPanel<\/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 provided there shows you information about the resource usage of your hosting account.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the current CloudLinux version and server configuration, the appearance and names of individual values may vary slightly.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2. Check the summary first<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before analyzing individual charts, you should look at the summary or the current status.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CloudLinux can indicate there whether your account has reached resource limits within a considered time period.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is much more informative for the diagnosis than simply noting that a chart once shows a high value.<\/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>Basic rule:<\/strong> Do not look for the highest peak in the chart first. First, check whether a limit was reached at all and at what time this happened.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">3. Select the analysis period<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When dealing with sporadic issues, the considered time period is particularly important.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, if your website was slow or inaccessible yesterday at around 2:30 PM, you should examine the resource usage specifically for that exact time period.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A sensible diagnostic procedure is:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Identify website issue\n        \u2193\nNote date and time\n        \u2193\nOpen resource utilization\n        \u2193\nSelect appropriate time period\n        \u2193\nCompare limits and metrics<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">A resource event at a completely different time usually does not explain your current website issue.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Understanding CPU Usage<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The CPU provides computing power. PHP scripts, database operations, and other processes require CPU time to execute their tasks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Increased CPU usage can be caused, for example, by:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>many simultaneous website visits<\/li>\n\n\n\n<li>computationally intensive PHP processes<\/li>\n\n\n\n<li>extensive database operations<\/li>\n\n\n\n<li>Imports and exports<\/li>\n\n\n\n<li>Backup or maintenance processes<\/li>\n\n\n\n<li>Cron jobs<\/li>\n\n\n\n<li>inefficient plugins or applications<\/li>\n\n\n\n<li>bot traffic<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">High CPU usage is initially just a metric. The decisive factor is whether the CPU limit applicable to the account is actually reached.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What happens when a CPU limit is reached?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When an account fully utilizes its assigned CPU performance, CloudLinux can limit further CPU usage.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Simplified, this means:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Application requires more CPU power\n        \u2193\nAccount CPU limit is reached\n        \u2193\nFurther processing is throttled\n        \u2193\nProcesses may take longer<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For visitors, this can manifest itself, for example, as a slower website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, a CPU limit does not necessarily mean that a process is immediately terminated with a visible error message.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Short CPU spike or persistent issue?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A short CPU spike can be completely normal for certain tasks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, an import can require significantly more computing power for a short time than normal website operation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A more critical pattern is like:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>CPU limit regularly reached\n\u2192 Website slow at the same time\n\u2192 Same situation repeats itself\n\u2192 Cause is reproducible<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Then you should investigate which process or application is causing the load.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Understand Physical Memory<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Physical Memory<\/strong> refers to the physical memory used by the processes of your hosting account within the CloudLinux environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This value is not the same as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>your hosting storage space<\/li>\n\n\n\n<li>the size of your website<\/li>\n\n\n\n<li>the PHP-<code>memory_limit<\/code><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This is a particularly important distinction.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Distinguish between physical memory and PHP memory_limit<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The PHP<code>memory_limit<\/code> limits the memory that a single PHP process may use according to its PHP configuration.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In contrast, the CloudLinux Physical Memory limit looks at the memory consumption of the hosting account's processes from a different level.<\/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 PHP configuration of a PHP process\n\nCloudLinux Physical Memory\n\u2192 Memory usage of the account processes within the LVE<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">A higher PHP-<code>memory_limit<\/code> therefore does not automatically increase the CloudLinux memory limit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain how to manage PHP limits 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>Important:<\/strong> When CloudLinux reports a memory limit, you shouldn't simply increase the PHP memory limit. This can actually make a resource issue more apparent because individual PHP processes are allowed to consume more memory.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">What can consume a lot of RAM?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Increased memory consumption can be caused, for example, by multiple simultaneously running PHP processes, extensive applications, or particularly memory-intensive tasks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical situations are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>large imports<\/li>\n\n\n\n<li>Image processing<\/li>\n\n\n\n<li>extensive WordPress or WooCommerce processes<\/li>\n\n\n\n<li>multiple parallel PHP requests<\/li>\n\n\n\n<li>Cron jobs<\/li>\n\n\n\n<li>Backup or maintenance processes<\/li>\n\n\n\n<li>faulty or inefficient application code<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Understand I\/O<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>I\/O<\/strong> stands for Input\/Output and simply describes the data rate at which processes can read or write data.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This affects file access, for example.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">High I\/O activity can occur, among other things, during the following tasks:<\/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>Cache generation<\/li>\n\n\n\n<li>certain data-intensive applications<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">What happens when an I\/O limit is reached?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a process requires more I\/O performance than is available for the account, data processing can be throttled accordingly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This can cause file operations or dependent processes to take longer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, an I\/O limit is not the same thing as a full storage space.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Storage full\n\u2192 there is no space for additional data\n\nI\/O limit reached\n\u2192 the input\/output data rate is limited<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">IOPS can be displayed separately<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the CloudLinux configuration, an additional value for <strong>IOPS<\/strong> displayed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">IOPS describes the number of input\/output operations per second and is therefore not identical to the amount of data transferred per second.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Simplified:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>I\/O\n\u2192 how much data is transferred per unit of time\n\nIOPS\n\u2192 how many individual input\/output operations occur per unit of time<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, many small file operations can produce a different resource profile than a few large file operations.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Understanding entry processes<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Entry Processes<\/strong> - often as <code>EP<\/code> \u2013 are among the CloudLinux values that are most frequently misunderstood.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">They simply describe the number of incoming processes entering or being simultaneously processed within the CloudLinux LVE environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This may include dynamic web requests in particular.<\/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> Entry processes do not match the number of your website visitors. A visitor is not automatically an entry process.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">Why Visitors and Entry Processes Are Not the Same<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A visitor can trigger multiple requests one after another. At the same time, different requests can take vastly different amounts of time to process.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, for the EP limit, the <strong>Simultaneity of relevant processes<\/strong> crucial and not simply the number of visitors per day.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, a website with many fast, well-cached requests can behave differently than a website with few, but very slow, dynamic requests.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What happens when the entry process limit is reached?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If too many corresponding processes have to be processed simultaneously and the EP limit is reached, additional requests cannot be processed normally.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this context, visitors can, for example, encounter errors such as:<\/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\">see.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We will cover the specific diagnosis and troubleshooting in the next article under <a href=\"\/en\/help\/web-hosting-cpanel\/resource-limit-is-reached\/\">Resource Limit Is Reached: Identify and Fix CloudLinux Limits<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Understand Number of Processes<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">CloudLinux can additionally limit the total number of processes for an account. This value is often referred to as <strong>Number of Processes<\/strong> or rather <code>NPROC<\/code> referred to as.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is not just about simultaneously incoming web requests.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the respective environment, different processes of the account can contribute to the process inventory.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is why <strong>Entry Processes and Number of Processes are not the same<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Compare Entry Processes and Number of Processes<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Value<\/th><th>Simply put<\/th><\/tr><\/thead><tbody><tr><td>Entry Processes (EP)<\/td><td>simultaneously occurring or processed incoming processes<\/td><\/tr><tr><td>Number of Processes (NPROC)<\/td><td>Total number of running processes of the account<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, an account can have a process issue without EP and NPROC necessarily exhibiting the same behavior at the same time.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Faults are particularly important for diagnosis<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In the CloudLinux analysis, in addition to current or average values, so-called <strong>Faults<\/strong> or limit events be relevant.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A fault shows in simplified terms that a resource limit has been reached.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is often more informative for the diagnosis than a chart whose line is merely close to the limit.<\/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>Practical Tip:<\/strong> If you want to know whether a resource limit was truly relevant, pay special attention to documented limit events and their timing.<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">100 % does not mean the same thing for every value<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Percentage displays must always be read in the context of the respective resource limit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a 100 % CPU reading in a hosting resource view does not automatically mean that the entire physical server is at 100 % capacity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It can refer to the resource assigned to your account.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, do not use percentages as a statement about the overall server utilization.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Differentiate between account limit and server load<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When your hosting account reaches a CloudLinux limit, it does not automatically follow that the entire hosting server is overloaded.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CloudLinux serves to isolate the resources of individual accounts from each other.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Simplified:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Account reaches its own resource limit\n\u2260\nentire server is busy<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This distinction is crucial when interpreting the values.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Averages can mask short peaks<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An average value over a longer period can look unremarkable, even though a short, sharp load peak occurred within that period.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If your website only had issues for a few minutes, you should therefore consider the most appropriate time frame possible and take limit events into account.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A single peak is not yet a diagnosis<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Assuming the CPU usage briefly spikes to a high value while:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>the website works normally<\/li>\n\n\n\n<li>no limits are documented<\/li>\n\n\n\n<li>no errors occur<\/li>\n\n\n\n<li>the value subsequently decreases again<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">That does not automatically require action.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A peak load can simply have been caused by a recently executed task.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Recurring limits are more relevant<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Much more interesting is a pattern like:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>every day around 02:00 AM\n\u2192 CPU spikes significantly\n\u2192 I\/O increases\n\u2192 limits are reached\n\u2192 website responds slowly at the same time<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Such a recurring pattern suggests taking a closer look at the processes running at that time.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Compare cronjobs with resource events<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If resource issues occur regularly at the same time, also check scheduled cron jobs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An import, export, backup, or synchronization process can lead to a recurring load pattern.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We explain how to investigate cron job issues 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\">Multiple cron jobs at the same time<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When multiple resource-intensive cron jobs start at the exact same time, their demands can add up.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>02:00 \u2192 Import\n02:00 \u2192 Export\n02:00 \u2192 Synchronization\n02:00 \u2192 Maintenance process<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the respective applications are flexible in time, staggering the start times can be useful.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not change application-preset schedules without verification, however.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Backups can require resources<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on the volume, backup and archiving processes can consume CPU, I\/O, and other resources.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If a peak load occurs during a backup, the temporal connection is relevant for this reason.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, that does not automatically mean that the backup is faulty.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Imports and exports can cause peak loads<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Large data imports and exports are typical examples of temporarily resource-intensive operations.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A WooCommerce product import, a large database operation, or the processing of many files can temporarily require significantly more resources than normal website operation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">WordPress plugins as a potential cause<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In WordPress, plugins can execute background tasks, database queries, or external connections.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If a resource issue begins immediately after installing or updating a plugin, this temporal correlation should be investigated.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This does not yet automatically prove the plugin is the cause.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can find a systematic conflict diagnosis under <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\">WooCommerce often requires more dynamic processing<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Online stores contain many areas that cannot simply be treated like static pages.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Shopping cart, checkout, customer account, orders, background tasks and various extensions can cause additional dynamic processing.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, a WooCommerce shop should not be compared with a simple information website based solely on the number of visitors.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Bots can consume resources<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Not only human visitors generate load.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bots, crawlers, and automated scanners can send many requests to a website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If unusual resource load occurs simultaneously with heavy traffic, access statistics or access logs may therefore also be relevant.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Many visitors do not automatically mean resource problems<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A high number of visitors alone says little about the required server resources.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Crucial factors include, among others:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>how many requests are made simultaneously<\/li>\n\n\n\n<li>how quickly PHP processes these<\/li>\n\n\n\n<li>how efficient database queries are<\/li>\n\n\n\n<li>what content can be cached<\/li>\n\n\n\n<li>which plugins or applications are involved<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A well-optimized website can therefore handle significantly more inquiries than a technically inefficient website with a comparable application.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Caching can reduce dynamic load<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If content does not need to be completely regenerated by PHP and the database on every request, caching can significantly reduce dynamic server load.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CURIAWEB provides a corresponding tool in cPanel with AccelerateWP.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can find more information at <a href=\"\/en\/help\/web-hosting-cpanel\/acceleratewp-explained\/\">AccelerateWP in cPanel explained<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Caching does not solve every resource problem<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A cache helps primarily with requests that can be usefully cached.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, it does not automatically resolve:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>faulty cron jobs<\/li>\n\n\n\n<li>extremely complex backend processes<\/li>\n\n\n\n<li>badly programmed database operations<\/li>\n\n\n\n<li>certain WooCommerce background tasks<\/li>\n\n\n\n<li>memory leaks or faulty code<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, do not activate additional cache systems indiscriminately if the actual cause is unknown.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Multiple cache plugins can be problematic<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">More caching does not automatically mean more speed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Multiple cache and optimization solutions working simultaneously can interfere with each other or create unnecessary complexity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, use a controlled configuration that matches the hosting environment.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">PHP version can affect resource usage<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">PHP versions differ, among other things, in terms of performance and software compatibility.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An outdated PHP version or one that is unsuitable for the application can therefore also be indirectly relevant for resource analysis.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At CURIAWEB, you generally manage a domain's PHP version 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\">Do not switch PHP just because a resource value is high. First, check your application's compatibility.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">PHP Memory Limit is not a performance setting<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A common mistake when dealing with a slow website is simply the PHP-<code>memory_limit<\/code> to increase significantly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The memory limit merely provides a PHP process with a maximum permitted memory framework.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It does not automatically make PHP faster and does not provide the hosting account with additional CPU performance.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Check error log in parallel<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a website shows errors at the same time, you should also examine the error log in addition to the CloudLinux metrics.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Under <a href=\"\/en\/help\/web-hosting-cpanel\/read-cpanel-error-log\/\">Read cPanel Error Log and find website errors<\/a> let's explain how you classify typical PHP and web server messages.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Resource issue or PHP error?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Both problems can cause similar symptoms.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Observation<\/th><th>Important checkpoint<\/th><\/tr><\/thead><tbody><tr><td>PHP Fatal Error<\/td><td>Error Log<\/td><\/tr><tr><td><code>Allowed memory size exhausted<\/code><\/td><td>PHP Memory Limit and Application<\/td><\/tr><tr><td>CloudLinux limit documented<\/td><td>Resource usage<\/td><\/tr><tr><td><code>Resource Limit Is Reached<\/code><\/td><td>CloudLinux Limits<\/td><\/tr><tr><td>Website occasionally slow<\/td><td>Compare timestamp with resources and logs<\/td><\/tr><tr><td>Storage full<\/td><td>Storage usage<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Do not equate CPU limit with a slow database<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When an application requires a lot of CPU, an inefficient database query may be involved. However, the CPU value alone does not prove this.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Conversely, a slow application can be delayed by external APIs, file access, or other factors without the CPU constantly running at its limit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The resource graphic shows you <strong>was<\/strong> is burdened \u2013 it does not automatically show <strong>what specific program code<\/strong> is the cause.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The CloudLinux display is not a process debugger<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">CloudLinux helps you narrow down resource bottlenecks by time and resource type.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, the ad says:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>CPU limit was reached at 2:32 PM<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">It does not automatically mean:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Plugin XYZ is to blame<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For the actual root cause analysis, you need to combine the timestamp with website activities, cron jobs, logs, updates, or other technical information.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What happened immediately before the resource problem<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the resource usage has only recently become noticeable, check changes such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>new plugin installed<\/li>\n\n\n\n<li>Plugin or theme updated<\/li>\n\n\n\n<li>new website imported<\/li>\n\n\n\n<li>Cron job set up<\/li>\n\n\n\n<li>Backup solution changed<\/li>\n\n\n\n<li>new marketing campaign launched<\/li>\n\n\n\n<li>Traffic has increased significantly<\/li>\n\n\n\n<li>WooCommerce extension activated<\/li>\n\n\n\n<li>PHP version changed<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The temporal connection is an important clue, but not yet proof.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Targeted reproduction of the peak load after modification<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If a specific action might be responsible for the high load, you can observe the process closely\u2014provided the action can be repeated safely.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Check resource usage\n\u2193\nNote time\n\u2193\nExecute affected action\n\u2193\nCheck resource usage again<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Do not execute payment, shipping, import, or other modifying processes multiple times if you do not know their behavior upon repetition.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Consider multiple websites in the same cPanel account<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When multiple domains or applications are operated within the same hosting account, they can share the account's resources.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">High resource usage therefore does not necessarily have to come from the website where you first notice the problem.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Consider all applications and background processes of the account in question.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Old or forgotten installations can generate resources<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An inactive WordPress test installation can still:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>be called by bots<\/li>\n\n\n\n<li>Run WP-Cron<\/li>\n\n\n\n<li>Load plugins<\/li>\n\n\n\n<li>process automatic tasks<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, if there are multiple installations in your hosting account, you should also consider older test systems.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Compare resource values after optimization<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Once you have found and fixed a specific cause, compare the resource usage under conditions that are as similar as possible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Before:\nCPU limit reached multiple times daily\n\nChange:\nfixed faulty background process\n\nAfter:\nno more CPU faults in the comparable period<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This allows you to judge much better whether the measure actually helped.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Do not perform multiple optimizations at the same time<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you simultaneously:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>you change PHP\nyou change the cache\nyou deactivate plugins\nyou move cron jobs\nyou optimize the database<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">and the load subsequently decreases, you do not know which measure was responsible for it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, proceed in a controlled and step-by-step manner with the diagnosis.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">When is a resource limit actually relevant?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A limit is particularly relevant when several factors come together:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>the limit is actually reached<\/li>\n\n\n\n<li>The event occurs repeatedly.<\/li>\n\n\n\n<li>the timing coincides with a website issue<\/li>\n\n\n\n<li>the behavior can be reproduced or assigned to a process<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A single brief peak load without visible effects, on the other hand, should not be overestimated.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Typical resources and their significance<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Resource<\/th><th>Meaning<\/th><th>Inspect first in case of a limit<\/th><\/tr><\/thead><tbody><tr><td>CPU<\/td><td>computing power<\/td><td>PHP processes, application, cron jobs, traffic<\/td><\/tr><tr><td>Physical Memory<\/td><td>Memory of the account processes<\/td><td>parallel\/memory-intensive processes<\/td><\/tr><tr><td>I\/O<\/td><td>Data rate during file operations<\/td><td>Backups, Archives, Imports, File Operations<\/td><\/tr><tr><td>IOPS<\/td><td>Number of I\/O operations<\/td><td>many small file operations<\/td><\/tr><tr><td>Entry Processes<\/td><td>simultaneously occurring\/processed processes<\/td><td>simultaneous dynamic requests<\/td><\/tr><tr><td>Number of Processes<\/td><td>Total number of running processes<\/td><td>Background processes, parallel tasks<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Systematically analyze CloudLinux values<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Note the date and time of the website issue.<\/li>\n\n\n\n<li>Open <strong>Metrics \u2192 Resource Usage<\/strong>.<\/li>\n\n\n\n<li>Select a suitable time period.<\/li>\n\n\n\n<li>Check if CloudLinux reports a reached resource limit.<\/li>\n\n\n\n<li>Identify the affected resource.<\/li>\n\n\n\n<li>Check faults or limit events.<\/li>\n\n\n\n<li>Compare their timing with the website issue.<\/li>\n\n\n\n<li>Check cron jobs, imports, backups, and other activities at this time.<\/li>\n\n\n\n<li>Also check the error log for website errors.<\/li>\n\n\n\n<li>Then specifically change only one possible cause.<\/li>\n\n\n\n<li>Compare the resource usage again after the change.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">What you should not do with high resource values<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Avoid, in particular, the following hasty decisions:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Globally increase PHP memory limit drastically<\/li>\n\n\n\n<li>Change PHP version without compatibility check<\/li>\n\n\n\n<li>disable multiple plugins at the same time<\/li>\n\n\n\n<li>Delete files on suspicion<\/li>\n\n\n\n<li>install multiple caching plugins<\/li>\n\n\n\n<li>Remove cron jobs randomly<\/li>\n\n\n\n<li>interpret a single peak as permanent overload<\/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>Practical Tip:<\/strong> Resource analysis is a temporal diagnosis. The question is not only \u201eWhich value is high?\u201c, but above all \u201eWhich limit was reached when, and what was happening at that exact moment?\u201c<\/p>\n<\/blockquote>\n\n\n\n<h2 class=\"wp-block-heading\">If the website is slow, but no limits are reached<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If CloudLinux shows no relevant limit events, you should not continue trying to force a resource issue.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A slow website can have numerous other causes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This includes, for example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>slow database queries<\/li>\n\n\n\n<li>external APIs<\/li>\n\n\n\n<li>large or poorly optimized images<\/li>\n\n\n\n<li>JavaScript in the browser<\/li>\n\n\n\n<li>Plugins or themes<\/li>\n\n\n\n<li>missing or inadequate caching<\/li>\n\n\n\n<li>DNS or network dependencies<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">CloudLinux is simply a potential cause that you were already able to narrow down better using the metrics.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">If the website is not reachable at all<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When a website is completely unreachable, you should not rely exclusively on the CloudLinux display.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">DNS, domain configuration, SSL, web server, PHP, application, and other layers can also be relevant.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We cover the complete diagnosis under <a href=\"\/en\/help\/web-hosting-cpanel\/website-unreachable\/\">Website unreachable: systematically diagnosing hosting errors<\/a>.<\/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\">If your hosting account regularly reaches resource limits and you cannot clearly identify the causing application or task, document the problem as precisely as possible.<\/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 or application<\/li>\n\n\n\n<li>Date and time of the problem<\/li>\n\n\n\n<li>affected resource<\/li>\n\n\n\n<li>visible limit events or faults<\/li>\n\n\n\n<li>visible behavior of the website<\/li>\n\n\n\n<li>whether the problem occurs regularly or only once<\/li>\n\n\n\n<li>recent changes<\/li>\n\n\n\n<li>cron jobs, imports, or other tasks running at this time<\/li>\n\n\n\n<li>possibly relevant error log entries<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The more precisely the time is known, the easier it is to associate a resource event with a specific activity.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Summary<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Under <strong>Metrics \u2192 Resource Usage<\/strong> can you see in the CURIAWEB cPanel how your hosting account uses the resources managed by CloudLinux.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Key metrics include CPU, physical memory, I\/O, optionally IOPS, entry processes, and the total number of processes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">These values must not be confused with storage space or bandwidth. Likewise, CloudLinux Physical Memory is not the same as PHP-<code>memory_limit<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For the diagnosis, not only high measured values are important. The decisive factor is in particular whether a resource limit was actually reached, when this happened, and whether the timing coincides with a visible website problem.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Entry Processes do not correspond to the number of your visitors. Even a CPU value of 100 % in the resource display does not automatically mean that the entire hosting server is fully utilized.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Brief load spikes can be normal during imports, backups, cron jobs, or other tasks. Recurring limit events combined with a slow or faulty website, on the other hand, should be investigated more closely.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Compare resource events with cron jobs, updates, traffic, error logs, and other activities at the same time. Then, change only one possible cause at a time and check whether the behavior improves.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The most important rule is: <strong>Do not look for the highest value, but connect the actual limit event with the timestamp and causing activity.<\/strong><\/p>","protected":false},"excerpt":{"rendered":"<p>Wenn eine Website zeitweise langsam reagiert, Prozesse abbrechen oder Fehler nur unter Last auftreten, solltest du neben PHP-Fehlern und Speicherplatz auch die verf\u00fcgbaren Hosting-Ressourcen pr\u00fcfen. CURIAWEB verwendet CloudLinux, um Hosting-Accounts voneinander zu isolieren und Ressourcen kontrolliert zuzuweisen. In cPanel kannst du unter Messwerte \u2192 Ressourcennutzung nachvollziehen, ob dein Account Ressourcenlimits erreicht hat und welche Ressourcen [&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-22620","docs","type-docs","status-publish","hentry","doc_category-webhosting-cpanel"],"year_month":"2026-10","word_count":3580,"total_views":"28","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\/22620","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=22620"}],"version-history":[{"count":1,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22620\/revisions"}],"predecessor-version":[{"id":22622,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22620\/revisions\/22622"}],"wp:attachment":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/media?parent=22620"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_category?post=22620"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_tag?post=22620"}],"curies":[{"name":"WP","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}