CPU/RAM limits reached in Plesk: how to check and reduce load (GARMTECH Hosting)

On GARMTECH Web Hosting, each hosting plan has resource limits (CPU, RAM, processes, etc.) to keep the server stable for all customers. If your website exceeds these limits, you may notice:

• Slow page loads or temporary timeouts
• Short “site unavailable” periods during spikes
• Notifications about high CPU/RAM usage in Plesk Monitoring (if enabled)

Step 1: Check the load in Plesk

1. Log in to My.GARMTECH and open your hosting service.
2. Click Login to Plesk.
3. In Plesk, look for Monitoring (left menu). Review CPU and memory graphs and note the time when the limit was reached.
4. Open Websites & Domains → select the affected domain → Logs to check for repeated requests, errors, or spikes.

Note: Some hosting plans may not show the Monitoring menu. In that case, use Logs (access log + error log) and your application analytics to identify what happened during the spike.

Step 2: Identify the typical cause

The most common reasons we see on shared hosting are:

• Bot traffic (brute force login attempts, XML-RPC abuse, aggressive crawlers)
• Uncached WordPress pages or multiple cache plugins fighting each other
• Heavy plugins/themes (page builders, security scanners, WooCommerce, statistics trackers)
• Background tasks (WordPress cron, backup jobs, image optimization running too often)
• Runaway scripts (infinite loops, broken PHP code, misconfigured redirects)

Step 3: Quick fixes that usually help

1. Enable LiteSpeed caching (WordPress): GARMTECH hosting uses LiteSpeed Enterprise. For WordPress, install/enable the LiteSpeed Cache plugin and turn on page cache.
2. Update PHP version: Plesk → Websites & Domains → domain → PHP Settings → choose a newer supported PHP version (if available for your plan).
3. Reduce “heavy” plugins: Disable plugins one by one and test. Replace multiple overlapping cache/security plugins with a simpler setup.
4. Limit brute-force traffic: Change the WordPress admin URL, enable reCAPTCHA on login forms, and consider IP-based rate limiting via a CDN (for example, Cloudflare).
5. Optimize images and database: Large images and bloated databases increase CPU usage. Clean revisions/transients and compress oversized images.
6. Check scheduled tasks: Plesk → Scheduled Tasks and WordPress cron. Remove duplicate or too-frequent jobs.

Step 4: When to upgrade (or move a workload)

If CPU/RAM usage is constantly high (not just a short spike), it usually means the site outgrew the current plan. In that case you can:

• Upgrade your hosting plan in My.GARMTECH (more resources for the same environment), or
• Move to a VPS if you need dedicated resources, custom services, or consistently high load.

Tip: Before upgrading, first fix caching and remove obvious spikes. A well-cached WordPress site can handle much more traffic with the same resources.