OutlineWiki PostgreSQL 16 Full-Text Search & Memory Tuning
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)
Default Postgres configs under-allocate shared_buffers on 8 GB wiki servers.
Outline Wiki relies on PostgreSQL 16 GIN tsvector indexes and JSONB document revision tables rather than a separate Elasticsearch cluster.
On OutlineWiki, our sizing formula allocates a deterministic 768 MB minimum to PostgreSQL on 4–8 GB VPS nodes while capping work_mem so concurrent searches never trigger OOM kills.
OutlineWiki Reference Configuration for PostgreSQL 16 Full-Text & RAM Tuning
# postgresql.conf overrides for 8 GB KVM 2 host (768 MB Postgres budget)
shared_buffers = 512MB
effective_cache_size = 2GB
work_mem = 8MB
maintenance_work_mem = 128MB
max_connections = 60
wal_level = replica
OutlineWiki Implementation Checklist: PostgreSQL 16 Full-Text & RAM Tuning
Phase 1: PostgreSQL 16 Full-Text & RAM Tuning
Set shared_buffers to 512 MB and maintenance_work_mem to 128 MB so GIN index rebuilds stay inside the 768 MB floor.
Phase 2: PostgreSQL 16 Full-Text & RAM Tuning
Keep max_connections at 60 and match Outline Node DATABASE_CONNECTION_POOL_MAX=25 to avoid idle connection bloat.
Phase 3: PostgreSQL 16 Full-Text & RAM Tuning
Schedule weekly VACUUM ANALYZE on documents and revisions tables to reclaim dead JSONB tuple space.
Phase 4: PostgreSQL 16 Full-Text & RAM Tuning
Monitor pg_stat_user_indexes to verify search queries hit GIN tsvector indexes instead of sequential scans.
OutlineWiki Infrastructure Recommendation for PostgreSQL 16 Full-Text & RAM Tuning
Reserve 25% host RAM for Linux page cache alongside Postgres buffers.
We recommend running this PostgreSQL 16 profile on NVMe-backed KVM instances such as Hostinger KVM 2 ($11.99/mo promo, 2026-11-12 rate) because GIN index writes and revision snapshots benefit directly from local NVMe IOPS.
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