8 Deterministic BotFoundry Process, RAM & /dev/shm Sizing Blueprints
Every blueprint in the BotFoundry catalog models deterministic process memory, Docker --shm-size pools, and unattended supervisor recovery from official runtime documentation.
Select Your Unattended Workload on BotFoundry
-
BP-01 // MQL5-EAOpen BotFoundry Runbook →
BotFoundry MT4 / MT5 Forex EA Multi-Instance RAM & Watchdog Runbook
We model MetaTrader 4 and MetaTrader 5 servers on BotFoundry by summing the 2.80 GB Windows Server 2022 RDP desktop base, 0.42 GB per active terminal64.exe process, DLL indicator buffers, and a 22% volatility cushion so news-candle tick bursts never freeze unattended EAs.
-
BP-02 // FREQ-DOCKEROpen BotFoundry Runbook →
BotFoundry Freqtrade & FreqAI Docker MemoryMax & Chrony NTP Runbook
Standard OHLCV Freqtrade containers occupy ~0.55–0.65 GB RSS on Ubuntu 24.04, whereas rolling FreqAI LightGBM/PyTorch retraining expands pandas DataFrames across 4–12 GB RAM and 100% CPU threads. On BotFoundry, we enforce hard Docker memory limits and APAC/EU region selection to avoid HTTP 451 exchange IP blocks.
-
BP-03 // PW-SHMOpen BotFoundry Runbook →
BotFoundry Headless Playwright & Puppeteer /dev/shm Cluster Sizing Runbook
Docker’s default 64 MB /dev/shm partition and unreaped renderer subprocesses crash unhardened Playwright deployments within hours. Our BotFoundry model allocates 0.78 GB per active BrowserContext group, enforces shm_size: "2gb" plus init: true, and pairs worker pools with high-RAM DDR5 KVM or Ryzen servers.
-
BP-04 // N8N-BULLOpen BotFoundry Runbook →
BotFoundry n8n Queue Mode, Redis BullMQ & PostgreSQL Sizing Runbook
Single-process SQLite n8n deployments stall whenever bursty CRM webhooks collide with multi-megabyte JSON Code nodes or AI chains. On BotFoundry, we size EXECUTIONS_MODE=queue topologies with dedicated webhook listeners, Redis AOF brokers, and PostgreSQL 16 workers on 8 GB to 32 GB DDR5 KVM slices.
-
BP-05 // HB-MMOpen BotFoundry Runbook →
BotFoundry Hummingbot V2 Market Making & DEX Gateway RAM Runbook
Standalone CEX Hummingbot containers run inside ~0.90 GB RAM, but full Hummingbot V2 stacks (EMQX MQTT broker + Backend API + Dashboard + Node.js DEX Gateway for Uniswap/Jupiter) push baseline memory past 5.5 GB. On BotFoundry, we pair 8–16 GB DDR5 tiers with 3.5GHz+ high-clock cores and kernel TCP keep-alive tuning.
-
BP-06 // DISCORD-ZGCOpen BotFoundry Runbook →
BotFoundry Discord Sharded Bot & Lavalink v4 Java 21 ZGC Sizing Runbook
Crossing 2,500 Discord guilds mandates WebSocket Gateway sharding, while Lavalink v4 must pace 20 ms UDP Opus audio packets without stop-the-world JVM garbage collection hiccups. On BotFoundry, we pre-touch fixed -Xms/-Xmx heaps under Java 21 Generational ZGC and cap Discord.js guild caches.
-
BP-07 // TG-BOTAPIOpen BotFoundry Runbook →
BotFoundry Telegram Local Bot API (2,000 MB) & Mini-App Webhook Runbook
Telegram’s hosted api.telegram.org endpoint caps bot uploads at 50 MB and throttles concurrent media transfers. On BotFoundry, we size self-hosted C++ TDLib telegram-bot-api containers unlocking 2,000 MB local zero-copy file handling alongside Redis + PgBouncer Mini-App backends.
-
BP-08 // SELENIUM-GRIDOpen BotFoundry Runbook →
BotFoundry Selenium Grid 4 Parallel Session, /dev/shm & Auto-Drain Runbook
Hosted browser-grid SaaS platforms bill $150–$600/mo per parallel WebDriver slot. Using BotFoundry’s strict 1 dedicated thread + 1.5 GB RAM per active session rule with shm_size: 2gb and automatic 50-session container draining, teams run 10 to 40+ parallel Chrome/Firefox sessions on flat-rate KVM or Ryzen hardware.