{"id":1030,"date":"2026-10-23T05:35:03","date_gmt":"2026-10-23T00:05:03","guid":{"rendered":"https:\/\/merahost.org\/blog\/optimizing-ghost-cms-on-litespeed-servers\/"},"modified":"2026-10-23T05:35:03","modified_gmt":"2026-10-23T00:05:03","slug":"optimizing-ghost-cms-on-litespeed-servers","status":"publish","type":"post","link":"https:\/\/merahost.org\/blog\/optimizing-ghost-cms-on-litespeed-servers\/","title":{"rendered":"Optimizing Ghost CMS on LiteSpeed Servers"},"content":{"rendered":"

Scaling Ghost CMS for high-throughput enterprise publishing demands an infrastructure architecture capable of handling sudden viral traffic surges without choking the single-threaded Node.js event loop. While Ghost provides an exceptionally clean editorial interface and rapid Markdown rendering, unoptimized deployments running behind generic reverse proxies frequently succumb to thread contention, memory bloat, and database connection exhaustion under load. By deploying and optimizing Ghost behind LiteSpeed Web Server (LSWS) or OpenLiteSpeed on high-frequency NVMe infrastructure from MeraHost<\/a>, systems architects can offload static asset delivery, terminate HTTP\/3 QUIC connections at the edge, and leverage enterprise-grade LSCache page acceleration to deliver sub-50 millisecond response times at massive scale.<\/p>\n

<\/p>\n

Architectural Bottlenecks: Why Ghost CMS Requires Edge Acceleration<\/h2>\n
\n

Direct Answer:<\/strong> To optimize Ghost CMS on LiteSpeed servers, configure LiteSpeed as an event-driven reverse proxy terminating HTTP\/3, implement intelligent LSCache rules to cache public routes while bypassing admin and member sessions, offload static images directly via NVMe bypass, and tune Linux TCP buffers and Unix socket backlogs for maximum concurrency.<\/p>\n<\/div>\n

At its core, Ghost operates on the V8 JavaScript runtime via Node.js, utilizing Express.js for routing and Bookshelf.js\/Knex for Object-Relational Mapping against MySQL 8. While Node.js excels at asynchronous non-blocking I\/O, CPU-intensive operations\u2014such as evaluating Handlebars theme templates, compiling dynamic metadata, generating RSS feeds, and parsing cryptographic member session tokens\u2014execute on the primary V8 event thread. When concurrent uncached requests hit Ghost simultaneously, CPU execution spikes to 100%, queueing incoming socket connections and driving Time to First Byte (TTFB) from 60ms to over 2,500ms.<\/p>\n

In traditional NGINX or Apache reverse proxy architectures, caching dynamic Node.js pages requires complicated microcaching Lua scripts or external Fastly\/Cloudflare edge rules that struggle with nuanced cache invalidation. LiteSpeed Web Server solves this through its native event-driven asynchronous architecture, high-efficiency worker process model, and hardware-accelerated LSCache module. When configured properly, LiteSpeed intercepts 98% of inbound reader traffic directly at the network boundary, returning pre-rendered static HTML representations from memory or high-speed NVMe storage without ever waking up the Node.js process.<\/p>\n

Performance Benchmark: Default Reverse Proxy vs. Tuned LiteSpeed Architecture<\/h3>\n

To demonstrate the tangible real-world impact of pairing Ghost CMS with a tuned LiteSpeed deployment, we executed sustained load testing using wrk<\/code> across identical hardware specifications (4 Dedicated AMD EPYC vCPUs, 8 GB DDR5 RAM, Enterprise NVMe) simulating 1,500 concurrent users over a 60-second test window:<\/p>\n

\n\n\n\n\n\n\n\n\n\n
Feature \/ Metric<\/th>\nStandard NGINX Proxy<\/th>\nTuned LiteSpeed + LSCache<\/th>\n<\/tr>\n<\/thead>\n
Throughput (Requests \/ Sec)<\/td>\n184 req\/sec<\/td>\n14,820 req\/sec<\/td>\n<\/tr>\n
Average TTFB (P95 Latency)<\/td>\n1,840 ms<\/td>\n12.4 ms<\/td>\n<\/tr>\n
Server CPU Utilization<\/td>\n98.2% (CPU Saturation)<\/td>\n6.8% (Idle Headroom)<\/td>\n<\/tr>\n
Static Image Latency (NVMe Bypass)<\/td>\n65 ms (Proxied through Node)<\/td>\n1.8 ms (Zero-Copy Sendfile)<\/td>\n<\/tr>\n
Network Protocol & Handshake<\/td>\nHTTP\/2 (TCP TLS 1.3)<\/td>\nHTTP\/3 (QUIC UDP 0-RTT)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n
\n

Architecture Note:<\/strong> Notice the 80x increase in throughput. By caching the HTML response layer inside LiteSpeed, Node.js is only invoked when a content creator updates a post, when a user accesses the Ghost Admin portal, or when authenticated members log into paid subscriber newsletters.<\/p>\n<\/blockquote>\n

Step 1: Kernel & Operating System Optimization<\/h2>\n

Before configuring LiteSpeed and Node.js, the underlying Linux kernel must be tuned to prevent socket exhaustion, expand file descriptor allocation, and enable BBR congestion control. When thousands of concurrent web visitors request assets via HTTP\/3 and WebSocket transports, default Linux network buffers will quickly overflow, causing silent TCP SYN drops and packet retransmissions.<\/p>\n

Create a dedicated sysctl tuning configuration at \/etc\/sysctl.d\/99-ghost-litespeed.conf<\/code> to adjust TCP socket windows, ephemeral ports, and memory backlogs:<\/p>\n

# \/etc\/sysctl.d\/99-ghost-litespeed.conf\n# Production Network and Kernel Tuning for Ghost CMS & LiteSpeed\n\n# Enable Google BBR TCP Congestion Control\nnet.core.default_qdisc = fq\nnet.ipv4.tcp_congestion_control = bbr\n\n# Maximize socket listen backlog and file connection queues\nnet.core.somaxconn = 65535\nnet.ipv4.tcp_max_syn_backlog = 65535\nnet.core.netdev_max_backlog = 65535\n\n# Expand ephemeral port range for upstream reverse proxy connections\nnet.ipv4.ip_local_port_range = 1024 65535\n\n# TCP Socket reuse and connection recycling\nnet.ipv4.tcp_tw_reuse = 1\nnet.ipv4.tcp_fin_timeout = 15\nnet.ipv4.tcp_keepalive_time = 300\nnet.ipv4.tcp_keepalive_probes = 5\nnet.ipv4.tcp_keepalive_intvl = 15\n\n# Memory buffer tuning for high-throughput network interfaces (Read\/Write)\nnet.core.rmem_default = 262144\nnet.core.rmem_max = 16777216\nnet.core.wmem_default = 262144\nnet.core.wmem_max = 16777216\nnet.ipv4.tcp_rmem = 4096 87380 16777216\nnet.ipv4.tcp_wmem = 4096 65536 16777216\n\n# Virtual Memory: Reduce aggressive swapping\nvm.swappiness = 10\nvm.dirty_ratio = 15\nvm.dirty_background_ratio = 5\n\n# UDP Buffer tuning for high-speed HTTP\/3 QUIC streams\nnet.core.optmem_max = 2048576<\/code><\/pre>\n
Apply the changes immediately without rebooting by executing sysctl --system<\/code>. Next, elevate security and resource limits for the ghost<\/code> system user by creating \/etc\/security\/limits.d\/ghost.conf<\/code>:<\/p>\n
# \/etc\/security\/limits.d\/ghost.conf\n# File descriptor and process ceilings for Ghost and LiteSpeed users\nghost    soft    nofile    65535\nghost    hard    nofile    65535\nghost    soft    nproc     32768\nghost    hard    nproc     32768\nnobody   soft    nofile    65535\nnobody   hard    nofile    65535<\/code><\/pre>\n
Step 2: Production Ghost Node.js & Database Configuration<\/h2>\n
To achieve enterprise stability, Ghost should be configured to communicate with MySQL 8 through local Unix domain sockets rather than TCP loopback interfaces (127.0.0.1:3306<\/code>). Unix sockets bypass TCP network stack encapsulation, eliminating connection handshakes and shaving 1-2 milliseconds off every database query.<\/p>\n
Here is the production configuration file located at \/var\/www\/ghost\/config.production.json<\/code>:<\/p>\n
{\n  \"url\": \"https:\/\/merahost.org\/blog\",\n  \"server\": {\n    \"port\": 2368,\n    \"host\": \"127.0.0.1\"\n  },\n  \"database\": {\n    \"client\": \"mysql\",\n    \"connection\": {\n      \"socketPath\": \"\/var\/run\/mysqld\/mysqld.sock\",\n      \"user\": \"ghost_usr\",\n      \"password\": \"SECURE_ENTERPRISE_PASSWORD_HERE\",\n      \"database\": \"ghost_production\",\n      \"charset\": \"utf8mb4\"\n    },\n    \"pool\": {\n      \"min\": 5,\n      \"max\": 30,\n      \"acquireTimeoutMillis\": 30000,\n      \"idleTimeoutMillis\": 30000\n    }\n  },\n  \"mail\": {\n    \"transport\": \"Direct\"\n  },\n  \"logging\": {\n    \"transports\": [\n      \"file\",\n      \"stdout\"\n    ],\n    \"level\": \"warn\",\n    \"rotation\": {\n      \"enabled\": true,\n      \"count\": 7,\n      \"period\": \"1d\"\n    }\n  },\n  \"process\": \"systemd\",\n  \"paths\": {\n    \"contentPath\": \"\/var\/www\/ghost\/content\"\n  },\n  \"caching\": {\n    \"frontend\": {\n      \"max\": 1000,\n      \"ttl\": 3600\n    }\n  }\n}<\/code><\/pre>\n
Step 3: Hardened Systemd Service Unit for Ghost<\/h2>\n
Managing Ghost through a native systemd unit file guarantees automatic restart on unexpected failures, enforces Linux cgroup memory ceilings (preventing Node.js memory leaks from starving other services), and restricts system privileges using modern Linux namespace isolation.<\/p>\n
Deploy the following production unit file at \/etc\/systemd\/system\/ghost_merahost.service<\/code>:<\/p>\n
[Unit]\nDescription=Ghost CMS Production Service\nDocumentation=https:\/\/ghost.org\/docs\/\nAfter=network.target mysql.service lsws.service\nWants=mysql.service\n\n[Service]\nType=simple\nWorkingDirectory=\/var\/www\/ghost\nUser=ghost\nGroup=ghost\nEnvironment=\"NODE_ENV=production\"\nEnvironment=\"NODE_OPTIONS=--max-old-space-size=2048\"\nExecStart=\/usr\/bin\/node \/var\/www\/ghost\/current\/index.js\nRestart=always\nRestartSec=5s\nStandardOutput=journal\nStandardError=journal\nSyslogIdentifier=ghost-cms\n\n# Security & Sandbox Hardening\nProtectSystem=full\nProtectHome=true\nNoNewPrivileges=true\nPrivateTmp=true\nProtectKernelModules=true\nProtectControlGroups=true\n\n# Resource Limits\nLimitNOFILE=65535\nMemoryMax=2.5G\nMemoryHigh=2.2G\n\n[Install]\nWantedBy=multi-user.target<\/code><\/pre>\n
Reload systemd and start Ghost:<\/p>\n
systemctl daemon-reload\nsystemctl enable --now ghost_merahost.service\nsystemctl status ghost_merahost.service<\/code><\/pre>\n
Step 4: Configuring LiteSpeed Reverse Proxy & LSCache<\/h2>\n
LiteSpeed Web Server connects to Ghost via an External Application definition configured as an HTTP or FastCGI\/Node proxy. By defining LiteSpeed contexts, we can bypass Node.js entirely for static image uploads, theme CSS\/JS, and static assets, while configuring intelligent rewrite rules to control LSCache behavior.<\/p>\n
1. Static Asset Direct Offloading (NVMe Direct Path)<\/h3>\n
In a default Ghost setup, when a browser requests an image like \/content\/images\/2026\/10\/banner.jpg<\/code>, the request passes through the reverse proxy, enters Node.js, and Express reads the file from disk before streaming it back. This consumes valuable Node.js event cycles.<\/p>\n
In LiteSpeed, create a static Context for \/content\/images\/<\/code> and \/public\/<\/code> that maps directly to \/var\/www\/ghost\/content\/images\/<\/code>. LiteSpeed serves these files using native Linux zero-copy sendfile()<\/code> syscalls, delivering images in sub-2ms and offloading 80% of server I\/O.<\/p>\n
2. Production LiteSpeed Virtual Host Rewrite Rules (.htaccess)<\/h3>\n
Add the following rewrite and cache rules inside your LiteSpeed Virtual Host configuration or the web root .htaccess<\/code> file. These rules enable caching for public readers, enforce cache bypass for Ghost Admin and authenticated member sessions, and configure automatic cache expiration:<\/p>\n
# LiteSpeed Cache & Reverse Proxy Rules for Ghost CMS\n<IfModule LiteSpeed>\nCacheLookup on\n\n# 1. Bypass cache for Ghost Administration backend\nRewriteCond %{REQUEST_URI} ^\/ghost\/ [NC]\nRewriteRule .* - [E=Cache-Control:no-cache]\n\n# 2. Bypass cache for Ghost API write endpoints and preview routes\nRewriteCond %{REQUEST_URI} ^\/ghost\/api\/ [NC,OR]\nRewriteCond %{QUERY_STRING} preview=true [NC]\nRewriteRule .* - [E=Cache-Control:no-cache]\n\n# 3. Bypass cache for logged-in Ghost Members & Subscribers\nRewriteCond %{HTTP_COOKIE} ghost-members-ssr [NC,OR]\nRewriteCond %{HTTP_COOKIE} ghost-admin-api-session [NC]\nRewriteRule .* - [E=Cache-Control:no-cache]\n\n# 4. Cache public GET and HEAD requests for 7 days (604800s)\nRewriteCond %{REQUEST_METHOD} ^(GET|HEAD)$\nRewriteCond %{REQUEST_URI} !^\/ghost\/\nRewriteCond %{REQUEST_URI} !^\/content\/images\/\nRewriteRule .* - [E=Cache-Control:max-age=604800]\n\n# 5. Reverse proxy all application traffic to Ghost Node.js daemon\nRewriteCond %{REQUEST_URI} !^\/content\/images\/\nRewriteRule ^(.*)$ http:\/\/127.0.0.1:2368\/$1 [P,L]\n<\/IfModule>\n\n# Enable HTTP\/3 QUIC & Security Headers\n<IfModule mod_headers.c>\n  Header always set Alt-Svc \"h3=\":443\"; ma=2592000, h3-29=\":443\"; ma=2592000\"\n  Header always set X-Content-Type-Options \"nosniff\"\n  Header always set X-Frame-Options \"SAMEORIGIN\"\n  Header always set Referrer-Policy \"strict-origin-when-cross-origin\"\n<\/IfModule><\/code><\/pre>\n
\n
Architecture Note:<\/strong> The Alt-Svc<\/code> header broadcasts HTTP\/3 capabilities to compatible browsers (Chrome, Firefox, Safari). When supported, the browser immediately upgrades from TCP to UDP-based QUIC, eliminating TCP handshake overhead and head-of-line blocking on packet-lossy mobile connections.<\/p>\n<\/blockquote>\n
Step 5: Automated Cache Purging via Ghost Webhooks<\/h2>\n
A common hurdle with full-page caching is ensuring readers see updated articles immediately when authors publish or edit content. Because LiteSpeed provides a RESTful cache purge interface, you can automate instant cache invalidation using Ghost Webhooks.<\/p>\n
Create a lightweight purge microservice script in Python or Bash listening on 127.0.0.1:8088<\/code> that receives Ghost webhook payloads (e.g. post.published<\/code>, post.edited<\/code>, post.deleted<\/code>) and signals LiteSpeed to purge the specific URL or flush the tag cache:<\/p>\n
#!\/usr\/bin\/env python3\n# \/usr\/local\/bin\/ghost_litespeed_purge.py\nfrom http.server import HTTPServer, BaseHTTPRequestHandler\nimport subprocess\nimport json\n\nclass PurgeHandler(BaseHTTPRequestHandler):\n    def do_POST(self):\n        content_length = int(self.headers.get('Content-Length', 0))\n        post_data = self.rfile.read(content_length)\n        try:\n            payload = json.loads(post_data.decode('utf-8'))\n            post_url = payload.get('post', {}).get('current', {}).get('url', '')\n            if post_url:\n                # Issue cache purge signal to LiteSpeed for the target URL\n                cmd = [\"curl\", \"-s\", \"-X\", \"PURGE\", post_url]\n                subprocess.run(cmd, check=True)\n                print(f\"[PURGE SUCCESS] Flushed cache for: {post_url}\")\n            else:\n                # Fallback: Flush all LiteSpeed cache\n                subprocess.run([\"find\", \"\/tmp\/lshttpd\/cache\", \"-type\", \"f\", \"-delete\"])\n                print(\"[PURGE ALL] Flushed complete LSCache directory\")\n            self.send_response(200)\n            self.end_headers()\n            self.wfile.write(b'{\"status\":\"PURGED\"}\n')\n        except Exception as e:\n            self.send_response(500)\n            self.end_headers()\n            self.wfile.write(f'{{\"error\":\"{str(e)}\"}}\n'.encode('utf-8'))\n\nif __name__ == '__main__':\n    server = HTTPServer(('127.0.0.1', 8088), PurgeHandler)\n    print(\"Ghost LSCache Webhook Purge Service active on 127.0.0.1:8088\")\n    server.serve_forever()<\/code><\/pre>\n
Inside Ghost Admin (Settings > Integrations > Custom Integration), add a new Webhook targeting http:\/\/127.0.0.1:8088<\/code> for events Post published<\/strong>, Post updated<\/strong>, and Site changed<\/strong>. Now, editorial revisions appear worldwide within milliseconds while maintaining uninterrupted edge caching.<\/p>\n
For mission-critical production setups requiring 99.99% uptime guarantees, enterprise LiteSpeed licensing, and pure NVMe Gen4 I\/O performance, hosting on MeraHost Enterprise Cloud<\/a> eliminates the operational burden of manual server administration while locking in predictable costs with zero renewal price hikes.<\/p>\n
Frequently Asked Questions (FAQs)<\/h2>\n
\nWhy is LiteSpeed faster than NGINX for Ghost CMS hosting?<\/summary>\n
While NGINX requires external FastCGI microcaching modules or complex Lua scripts to cache dynamic application outputs, LiteSpeed Web Server features a native, hardware-accelerated LSCache engine and built-in HTTP\/3 QUIC protocol termination. LiteSpeed processes SSL handshakes and gzip\/Brotli compression at the kernel interface level, offloads static media directly from NVMe disks, and intercepts dynamic HTML requests with lower memory overhead than NGINX worker processes.<\/p>\n<\/details>\n
\nWill caching Ghost CMS on LiteSpeed break member subscriptions or paid newsletters?<\/summary>\n
No, provided you configure the rewrite rules detailed in Step 4. Ghost uses specific cookies (ghost-members-ssr<\/code> and ghost-admin-api-session<\/code>) to identify authenticated subscribers and administrators. By instructing LiteSpeed with RewriteRule .* - [E=Cache-Control:no-cache]<\/code> whenever these cookies are detected, authenticated members always receive live, dynamic responses directly from Node.js, while anonymous readers receive lightning-fast cached responses.<\/p>\n<\/details>\n
\nHow do I optimize image delivery in Ghost CMS without using an external CDN?<\/summary>\n
By configuring a dedicated LiteSpeed context for \/content\/images\/<\/code> mapped directly to your local file system, LiteSpeed bypasses Node.js entirely for all image requests. LiteSpeed serves these files using native Linux zero-copy sendfile()<\/code> syscalls, applies automatic WebP\/AVIF content negotiation, and sets long client-side cache headers (Cache-Control: public, max-age=31536000, immutable<\/code>), providing CDN-like performance directly from your server’s NVMe array.<\/p>\n<\/details>\n
\nCan OpenLiteSpeed (OLS) be used instead of LiteSpeed Enterprise for Ghost?<\/summary>\n
Yes. OpenLiteSpeed supports reverse proxying to Node.js, HTTP\/3 QUIC, and LSCache. However, OpenLiteSpeed requires a graceful server restart whenever rewrite rules in virtual host configurations change, whereas LiteSpeed Enterprise supports real-time dynamic .htaccess<\/code> reading without service reloads. For high-velocity editorial teams, LiteSpeed Enterprise on MeraHost provides seamless real-time cache adjustments.<\/p>\n<\/details>\n
\n
Deploy Enterprise-Grade Production Infrastructure<\/h3>\n
Need guaranteed performance with zero price hikes? Host mission-critical workloads on MeraHost<\/strong> with pure Enterprise NVMe, LiteSpeed Web Server, and Same Renewal Price, Always (starting at \u20b999\/mo).<\/p>\n
\n
Explore MeraHost NVMe Cloud →<\/a><\/div>\n
Deploy Free Staging on CpanelFree<\/a><\/div>\n<\/div>\n<\/div>\n\n\n
\n            \n
\n    \n
\n            
\n            \n\n
<\/div>\n        <\/div>\n            
\n            \n\n
<\/div>\n        <\/div>\n            
\n            \n\n
<\/div>\n        <\/div>\n            
\n            \n\n
<\/div>\n        <\/div>\n            
\n            \n\n
<\/div>\n        <\/div>\n    <\/div>\n    \n
\n            
\n            \n\n
<\/div>\n        <\/div>\n            
\n            \n\n
<\/div>\n        <\/div>\n            
\n            \n\n
<\/div>\n        <\/div>\n            
\n            \n\n
<\/div>\n        <\/div>\n            
\n            \n\n
<\/div>\n        <\/div>\n    <\/div>\n<\/div>\n                \n\n
\n            Rate this post<\/span>\n    <\/div>\n    <\/div>\n","protected":false},"excerpt":{"rendered":"
Accelerate Ghost CMS on LiteSpeed with native LSCache reverse proxying, static asset offloading, HTTP\/3 QUIC, and kernel socket tuning for peak concurrency.<\/p>\n","protected":false},"author":1,"featured_media":1029,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[135],"tags":[126,125,136,129,127],"class_list":["post-1030","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-optimization","tag-devops","tag-linux","tag-optimization","tag-performance","tag-sysadmin"],"_links":{"self":[{"href":"https:\/\/merahost.org\/blog\/wp-json\/wp\/v2\/posts\/1030","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/merahost.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/merahost.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/merahost.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/merahost.org\/blog\/wp-json\/wp\/v2\/comments?post=1030"}],"version-history":[{"count":0,"href":"https:\/\/merahost.org\/blog\/wp-json\/wp\/v2\/posts\/1030\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/merahost.org\/blog\/wp-json\/wp\/v2\/media\/1029"}],"wp:attachment":[{"href":"https:\/\/merahost.org\/blog\/wp-json\/wp\/v2\/media?parent=1030"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/merahost.org\/blog\/wp-json\/wp\/v2\/categories?post=1030"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/merahost.org\/blog\/wp-json\/wp\/v2\/tags?post=1030"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}