OutlineWiki Redis Pub/Sub & 12MB Live Editor Socket Sizing
Hostinger KVM NVMe
OutlineWiki 8GB pick (90,000 IOPS) — KVM 4 (4 vCPU / 16GB DDR5 / 200GB NVMe)
InterServer Price-Lock KVM & ZFS
Low-RTT node for outline Node.js + Hocu (19 ms CRDT sync)
UltaHost Dedicated EPYC VDS
Steady OutlineWiki secondary tier (25–100 collaborative editors)
Uncapped Redis BullMQ queues silently consume host RAM during bulk exports.
Every concurrent editor typing in Outline Wiki holds an open Yjs WebSocket channel inside Node.js while Redis coordinates Pub/Sub awareness states and BullMQ webhook jobs.
On OutlineWiki, we allocate 256 MB to Redis plus 12 MB per active editor socket on top of the 950 MB Node.js baseline.
OutlineWiki Reference Configuration for Redis Pub/Sub & 12MB WebSocket Sizing
redis-server \
--maxmemory 256mb \
--maxmemory-policy noeviction \
--appendonly yes \
--appendfsync everysecOutlineWiki Implementation Checklist: Redis Pub/Sub & 12MB WebSocket Sizing
Phase 1: Redis Pub/Sub & 12MB WebSocket Sizing
Always use maxmemory-policy noeviction on OutlineWiki Redis instances so BullMQ job keys are never silently dropped.
Phase 2: Redis Pub/Sub & 12MB WebSocket Sizing
Calculate collab_ws_mb = editors * 12; for 80 concurrent editors, budget 960 MB WebSocket heap on top of 950 MB base.
Phase 3: Redis Pub/Sub & 12MB WebSocket Sizing
Enable appendonly yes with everysec fsync to preserve pending notification and search indexing jobs across restarts.
Phase 4: Redis Pub/Sub & 12MB WebSocket Sizing
Increase Node --max-old-space-size only when total editors exceed 120 concurrent WebSocket connections.
OutlineWiki Infrastructure Recommendation for Redis Pub/Sub & 12MB WebSocket Sizing
Never set Redis policy to allkeys-lru on BullMQ job queues.
Our sizing formula on OutlineWiki verifies that 40 concurrent editors require 480 MB of WebSocket headroom, fitting comfortably inside an 8 GB VPS alongside PostgreSQL, MinIO, and Authentik OIDC.
OutlineWiki Hardware Ledger: NVMe Throughput vs Base Price
Packet-to-Disk Path for outline Node.js + Hocuspocus Yjs CRDT + OIDC on OutlineWiki
[+] Key Infrastructure Pros
- Keeps outline.env buffers stable at 100 collaborative editors via 8GB compute.
- Protects 19 ms CRDT sync objectives under heavy Postgres tsvector document graph + MinIO assets writes (90,000 IOPS).
- Trims OutlineWiki 3-year infrastructure bills 70%–85% versus metered SaaS seats.
[-] Operational Constraints
- Unlocking $10.49/mo on Hostinger KVM NVMe depends on annual commitment rather than 1m billing.
- Base OS templates need outline.env tuning (WEB_CONCURRENCY=4 & COLLABORATION_MAX_CLIENTS=150) before peak load.
Deploy This OutlineWiki Stack If
- DevOps squads standardizing outline Node.js + Hocuspocus Yjs CRDT + OIDC (100 collaborative editors) on KVM nodes.
- Builders needing root access to set WEB_CONCURRENCY=4 & COLLABORATION_MAX_CLIENTS=150 in outline.env.
When To Choose Alternatives
- Two-day load tests where InterServer Price-Lock KVM & ZFS pay-per-hour beats annual commitments.
- Mandates requiring vendor-staffed 24/7 NOC contracts with zero SSH access.
$10.49/mo