BOTFOUNDRY // DETERMINISTIC EQUATIONS & SOURCE GOVERNANCE
BotFoundry Deterministic 4-Layer RAM, /dev/shm & Watchdog Sizing Methodology
We model long-running 24/7 stateful processes on BotFoundry — MetaTrader 4/5 terminals, Freqtrade/Hummingbot containers, Playwright Chromium clusters, and n8n BullMQ workers — using transparent memory math derived from official software documentation and public hosting specifications retrieved 2026-11-12.
BotFoundry Core Equation in src/sizer-engine.mjs
BotFoundry 4-Layer DDR5 Sizing Formula
RAM_Total = OS_Kernel + Shared_Runtime_&_Shm + (Instances × Heap_Per_Unit × Density_Mult) + Volatility_Buffer (20%–30%)
-
01 // 4-LAYER MEMORY EQUATION
How BotFoundry Separates OS Kernel, Runtime/Shm, Instance Heaps & Volatility Headroom
Our sizer engine in src/sizer-engine.mjs calculates four distinct layers: (1) OS base footprint (0.65 GB for Ubuntu 24.04 headless systemd vs 2.80 GB for Windows Server 2022 RDP GUI), (2) shared runtime overhead (Docker Engine, Wine64/Xvfb, Redis/PostgreSQL, plus /dev/shm allocation), (3) active worker count multiplied by documented per-instance RSS (0.36 GB to 0.78 GB) and chart/DOM density (0.85x lean, 1.00x standard, 1.35x heavy), and (4) a 20%–30% burst buffer (minimum 0.80 GB) to absorb market-open volatility without OOM kills.
-
02 // CHROMIUM /DEV/SHM & CGROUP V2
Why BotFoundry Enforces --shm-size=2g, tini PID 1, and systemd MemoryMax Bounds
Standard cloud calculators ignore shared-memory exhaustion and zombie subprocesses. Because Docker mounts /dev/shm at 64 MB by default, Chromium V8 and Skia compositors crash on large DOM trees even when 12 GB of host RAM sits free. We bake explicit --shm-size=2g (scaling to 4g–8g at high concurrency), init: true zombie reaping, and systemd MemoryMax cgroup ceilings directly into our sizing outputs.
-
03 // HONEST TELEMETRY BOUNDARY
Separating Deterministic Spec Math from Pending Live Network Logs
BotFoundry never fabricates hands-on lab ping charts. Regional guidance reflects publicly documented exchange API geographies (such as non-US Tokyo/Singapore regions avoiding HTTP 451 blocks, or matching North American/European broker server zones). Wherever live 72-hour ICMP/TCP latency or hypervisor vmstat steal logs are still direct host-level telemetry verification on your target instance, we mark those /compare/ pages unindexed.
-
PUBLIC TARIFF CITATION & FTC DISCLOSURE
How BotFoundry Audits Public Vendor Pricing (2026-11-12) & Separates Partner Links
Plan specs and starting monthly rates are cited from official public pricing pages (Vultr, Hostinger, UltaHost, InterServer, ChemiCloud) retrieved on 2026-11-12; promotional and renewal rates can change, so always verify at checkout. Outbound /go/ links may earn BotFoundry a referral commission at zero extra cost to buyers without altering any formula thresholds.