Working within a shared environment.
THE LIMITS
CPU time, memory, entry processes, and disk I/O, each with a plan allowance.
Entry processes is the one developers most often hit: it limits concurrent requests, so a slow page under load queues rather than serving.
WHERE TO SEE THEM
cPanel > Resource Usage, with a Details view showing which limit was reached and when.
WHAT CAUSES LIMITS TO BE HIT
Uncached pages running full application code on every request A slow query holding a connection open Long-running requests that should be background jobs External API calls without timeouts, holding processes open Bot traffic
WHAT TO DO ABOUT IT
Cache aggressively Move slow work to queues Set timeouts on external calls Add database indexes Reduce per-request memory
WHAT NOT TO DO
Assume you need a bigger plan before profiling. A single unindexed query can consume more resources than a plan upgrade would provide.
WRITING FOR SHARED HOSTING
Assume constrained memory and short execution limits. Code written that way runs better everywhere.
