{"id":13334,"date":"2026-08-30T21:10:35","date_gmt":"2026-08-30T19:10:35","guid":{"rendered":"https:\/\/mybox.com\/help\/?post_type=manual_kb&#038;p=13334"},"modified":"2026-08-30T21:10:40","modified_gmt":"2026-08-30T19:10:40","slug":"site-web-resurse-limite-audit-lista-de-verificare-fisiere-procese-conexiuni-si-cozi-de-asteptare","status":"publish","type":"manual_kb","link":"https:\/\/mybox.com\/help\/ro\/knowledgebase\/website-resource-limits-audit-checklist-files-processes-connections-and-queues\/","title":{"rendered":"List\u0103 de verificare pentru auditul limitelor de resurse ale site-ului web: fi\u0219iere, procese, conexiuni \u0219i cozi de a\u0219teptare"},"content":{"rendered":"<div class=\"translation-block translation-block-merged\">\n<p class=\"wp-block-paragraph\">Intermittent website slowness does not always mean that a hosting limit has been reached. The same symptom can come from a slow application, an inefficient database query, a scheduled task, a traffic spike, or an issue outside the website environment.<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_86 ez-toc-wrap-left counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/website-resource-limits-audit-checklist-files-processes-connections-and-queues\/#Start_with_a_clear_incident_record\" >Start with a clear incident record<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/website-resource-limits-audit-checklist-files-processes-connections-and-queues\/#Check_storage_and_file_counts\" >Check storage and file counts<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/website-resource-limits-audit-checklist-files-processes-connections-and-queues\/#Inspect_PHP_workers_and_running_processes\" >Inspect PHP workers and running processes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/website-resource-limits-audit-checklist-files-processes-connections-and-queues\/#Review_concurrent_connections_and_queues\" >Review concurrent connections and queues<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/website-resource-limits-audit-checklist-files-processes-connections-and-queues\/#Audit_database_use_and_active_queries\" >Audit database use and active queries<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/website-resource-limits-audit-checklist-files-processes-connections-and-queues\/#Check_scheduled_jobs_and_task_queues\" >Check scheduled jobs and task queues<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/website-resource-limits-audit-checklist-files-processes-connections-and-queues\/#Compare_traffic_with_resource_usage\" >Compare traffic with resource usage<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/website-resource-limits-audit-checklist-files-processes-connections-and-queues\/#Use_the_evidence_to_choose_the_next_action\" >Use the evidence to choose the next action<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Start_with_a_clear_incident_record\"><\/span>Start with a clear incident record<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Record when the site is slow, which pages or actions are affected, and whether the issue is constant or intermittent. Note whether the problem affects visitors, administrators, forms, uploads, or database-backed pages. The timing matters because a recurring slowdown may match a scheduled task, while a short burst may match a traffic increase or a temporary connection surge.<\/p>\n\n\n\n<\/div>\n\n<div id=\"mybox-3075103560\" class=\"mybox-content mybox-entity-placement\"><div class=\"early-access-banner-inpost\">\r\n  <div class=\"banner-left-inpost\">\r\n    <div class=\"icon-box-inpost\">\r\n      <img decoding=\"async\" src=\"https:\/\/mybox.com\/help\/wp-content\/uploads\/2026\/02\/square-info-icon.svg\" alt=\"Info\">\r\n    <\/div>\r\n    <div class=\"text-box-inpost\">\r\n      <span class=\"label-inpost\"><span class=\"translation-block translation-block-banner-text\">Acces timpuriu<\/span><\/span>\r\n      <h4><span class=\"translation-block translation-block-banner-text\">Mai ave\u021bi nevoie de ajutor?<\/span><\/h4>\r\n      <p><span class=\"translation-block translation-block-banner-text\">Contacta\u021bi echipa noastr\u0103 de servicii pentru clien\u021bi.<\/span><\/p>\r\n    <\/div>\r\n  <\/div>\r\n\r\n  <div class=\"banner-right-inpost\">\r\n    <a href=\"https:\/\/panel.mybox.com\/helpdesk2\/v\/list\/\" class=\"banner-button-inpost\"><span class=\"translation-block translation-block-banner-text\">Trimite mesaj<\/span><\/a>\r\n  <\/div>\r\n<\/div><\/div>\n\n<div class=\"translation-block translation-block-merged\"><p class=\"wp-block-paragraph\">Use the same observation period for each part of the audit. Collect values while the site is working normally and again during a slowdown. This gives you a baseline and an incident sample instead of relying on a single reading.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Check_storage_and_file_counts\"><\/span>Check storage and file counts<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Record total storage use and compare it with the storage limit shown for the hosting environment. Separate the main areas where possible, such as website files, uploads, backups, logs, and temporary files. A storage warning is justified when total use is close to the plan limit or continues to grow between checks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Also record the number of files and directories. A site can have available storage while still creating management or performance pressure through a very large file count. Compare the current count with earlier records and identify which directory is growing. Pay particular attention to upload folders, generated cache files, logs, and backup locations.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not treat storage capacity and file count as the same resource. A site may need file cleanup when storage is not yet full, and it may need more storage when a small number of large files are responsible for the increase.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Inspect_PHP_workers_and_running_processes\"><\/span>Inspect PHP workers and running processes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Record the number of PHP workers or application processes in use during normal activity and during the incident. If all available workers are busy while requests wait, the application may be reaching a process ceiling. This pattern supports optimization or a hosting-plan review when it repeats during ordinary traffic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If workers remain busy because requests take a long time, the worker count alone does not identify the cause. Review the pages, scripts, or actions holding those workers. A slow application can consume the available workers without proving that the hosting environment itself is undersized.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Include other running processes in the record. Note their start time, duration, and purpose where that information is available. A process that remains active through repeated checks deserves investigation, especially when it overlaps with user-facing slowness.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Review_concurrent_connections_and_queues\"><\/span>Review concurrent connections and queues<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Record active connections during normal periods and during an incident. Include web, database, and other relevant connection types shown by the environment. A connection warning is justified when active connections repeatedly approach the stated limit, or when requests remain queued while connection capacity is occupied.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Compare the connection pattern with traffic. High connections during a traffic spike may be a demand event. High connections with normal traffic may point to slow requests, an application process that does not release connections promptly, or database work that is taking too long.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Keep connection counts separate from process counts. A site can have available PHP workers but still wait for database connections. It can also have free database connections while application workers are occupied by slow code.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Audit_database_use_and_active_queries\"><\/span>Audit database use and active queries<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Record database activity during the slowdown, including active processes and queries that remain running. A stuck or unoptimized SQL query is a common cause of a slow or unresponsive website, and identifying and ending the process can restore stability in the affected environment. See <a href=\"https:\/\/mybox.com\/help\/ro\/baza-de-cunostinte\/cum-sa-verificati-si-sa-inchideti-procesele-in-mysql\/\">how to check and end processes in MySQL<\/a> for the relevant process review procedure.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Compare the same query or process across multiple checks. A query that finishes quickly is different from one that remains active and blocks other work. If database activity rises only when a specific page, form, or administrator action is used, investigate that application path before treating the issue as a general hosting limit.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Check_scheduled_jobs_and_task_queues\"><\/span>Check scheduled jobs and task queues<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">List scheduled jobs, their run times, frequency, purpose, and duration. A CRON job is a time-based task scheduler used for repetitive actions such as database backups, scheduled emails, and cache cleanup. These tasks use server resources while they run, so compare their execution times with the incident record. The <a href=\"https:\/\/mybox.com\/help\/ro\/baza-de-cunostinte\/lista-de-verificare-a-resurselor-pentru-sarcinile-cron-ale-site-ului-web-pentru-a-preveni-depasirea-limitelor-de-gazduire-de-catre-sarcinile-programate\/\">Website Cron Job Resource Checklist<\/a> provides a focused method for reviewing this activity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Look for jobs that overlap, run longer than expected, or leave repeated work in a queue. A queue that grows during each run is a warning sign for optimization. If the queue grows only during unusually high traffic, compare both events before changing the hosting plan.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Compare_traffic_with_resource_usage\"><\/span>Compare traffic with resource usage<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Record traffic for the same periods as the resource readings. Compare normal traffic with the number of active processes, connections, PHP workers, database queries, and queued tasks. A resource ceiling is more likely when usage reaches the plan limit at ordinary traffic and the pattern repeats. A traffic spike is a stronger explanation when resource use rises only during an unusual increase in visits or requests.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Use_the_evidence_to_choose_the_next_action\"><\/span>Use the evidence to choose the next action<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Plan limit reached at normal traffic:<\/strong> optimize the application and review whether a hosting-plan change is needed.<\/li>\n\n\n\n<li><strong>Slow queries or persistent database processes:<\/strong> investigate the affected query or application action before changing the plan.<\/li>\n\n\n\n<li><strong>Workers or connections occupied by long requests:<\/strong> identify the requests holding them and review the application path.<\/li>\n\n\n\n<li><strong>Scheduled jobs overlap with the slowdown:<\/strong> review the job duration, frequency, and resource use.<\/li>\n\n\n\n<li><strong>Usage follows a traffic spike:<\/strong> compare the event with normal readings before treating it as a permanent capacity need.<\/li>\n\n\n\n<li><strong>Resource readings remain normal during the incident:<\/strong> the slowdown is less consistent with a resource ceiling. Use the timing and process evidence to distinguish application, query, task, traffic, and provider-side causes.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Repeat the audit after each optimization or hosting-plan change. Keep the same measurements so the new results can be compared with the original baseline and incident sample.<\/p>\n<\/div>","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"template":"","format":"standard","manualknowledgebasecat":[125],"manual_kb_tag":[],"class_list":["post-13334","manual_kb","type-manual_kb","status-publish","format-standard","hentry","manualknowledgebasecat-websites"],"_links":{"self":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/13334","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb"}],"about":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/types\/manual_kb"}],"author":[{"embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/13334\/revisions"}],"predecessor-version":[{"id":13351,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/13334\/revisions\/13351"}],"wp:attachment":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/media?parent=13334"}],"wp:term":[{"taxonomy":"manualknowledgebasecat","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manualknowledgebasecat?post=13334"},{"taxonomy":"manual_kb_tag","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb_tag?post=13334"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}