Performance & Caching
Performance & Caching
Object caching, resource limits and diagnosing a slow site.
Object caching, resource limits and diagnosing a slow site.
Enable Redis object caching
Turn on Redis in cPanel and point LiteSpeed Cache at it, so WordPress stops repeating the same database queries on every page load.
Which object cache should I use?
Redis is the object cache available on WebGee hosting. Memcached has been retired, so the choice that used to exist no longer does.
Memcached is no longer available
Memcached has been retired on WebGee shared and reseller hosting. Use Redis object caching instead, which is a drop-in replacement.
Find what is making your site slow
Use PHP X-Ray in cPanel to trace slow plugins, database queries and external calls, and identify the real bottleneck in your application.
Fix a 503 "Resource Limit Reached" error
A 503 means your account hit its CPU, memory or entry process limit. How to find what is consuming them and bring usage back down.
You received a resource usage alert
WebGee emails you when an account reaches its resource limits. How to find what caused it and what to do about it.
Fix the Redis "OOM command not allowed" error
Redis has its own memory limit, separate from your account's. When the cache fills, writes fail with this error until it is cleared or raised.
CloudLinux and LVE limits explained
Every account runs in its own container with fixed CPU, memory and process limits. What each limit does when you reach it.
What entry processes are
Entry processes count requests being handled simultaneously, not visitors. Why a slow site hits the limit long before a fast one does.