v1.6.0: Shared Hosting Performance

v1.6.0 focuses on one problem: shared hosting. Many users run WordPress on shared or low-resource VPS environments where CPU, RAM, and concurrent connections are tightly constrained. Previous versions were tuned for reliability on mid-tier servers but could trigger HTTP 522, 524, and 503 errors on smaller setups. This release targets each of those failure modes directly.

Conservative Server Tier Detection

The automatic server tier detection has been recalibrated to err on the side of caution. The plugin now classifies servers more conservatively, which means lower default batch sizes on shared hosting — reducing the risk of CPU spikes that cause the web server to drop connections with HTTP 522 errors.

Server-Tier-Aware Image Throttling

Image importing is one of the most resource-intensive parts of a migration. v1.6.0 introduces per-tier throttling for image downloads, slowing the rate on low-tier servers to prevent sustained CPU load that leads to 522 crashes. Higher-tier servers retain their previous throughput.

HTTP 503 Recovery

HTTP 503 (Service Unavailable) is now treated as a server overload signal rather than a generic error. When a 503 is received, the plugin enters a cooldown period and reduces the batch size before retrying — the same pattern used for 524 and 504 errors. This prevents the plugin from hammering an already-overloaded server.

80-Second Circuit Breaker for Cloudflare 524

Cloudflare terminates requests that exceed 100 seconds with a 524 error. v1.6.0 adds an 80-second client-side circuit breaker: if a batch hasn't completed within 80 seconds, the request is aborted and retried with a smaller batch size, before Cloudflare can terminate it. This eliminates a class of timeout failures on Cloudflare-proxied sites.

Actual RAM Detection

Previous versions estimated available memory from PHP's memory_limit setting. v1.6.0 reads actual system RAM to make more accurate decisions about batch sizing. On small VPS instances with 512MB or 1GB of total RAM, this prevents out-of-memory crashes that the PHP memory limit alone couldn't predict.

Manual Batch Size Override

Power users can now override the automatic batch size directly from the sync interface. The override includes risk warnings and enforces API-safe caps to prevent configurations that would reliably cause timeouts. This is intended for advanced users who have already profiled their server's capacity and want precise control.

v1.6.0 is a fully backwards-compatible update. No settings or data changes are required. Download the latest release from the GitHub repository.