BF BotFoundry
BotFoundry / 8 Bot Blueprints / hummingbot-market-making
BOTFOUNDRY HUMMINGBOT RUNBOOK • TCP BBR & DEX GATEWAY HEAP

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.

Inspect Vultr Specs for HB-MM via BotFoundry → Compare UltaHost Tiers via BotFoundry → Load Preset in BotFoundry RAM Sizer →

BotFoundry Deterministic vCPU, RAM & Guard Matrix (BP-05 // HB-MM)

Public rates retrieved 2026-11-12 from official vendor pricing pages cited below; promotional & renewal prices may change — always verify exact specs, term length, and renewal rates on the vendor’s official checkout page.

Concurrency Scale vCPU DDR5 RAM OS / Runtime /dev/shm & Watchdog Guard Public Tier Match (2026-11-12)
1–2 Standalone CEX Bots 2 vCPU 3.5GHz+ HF 4 GB DDR5 Ubuntu 24.04 Headless tcp_slow_start=0 + chrony Vultr HF 4GB ($24/mo)
4–8 V2 Strategy Bots 3–4 vCPU 3.5GHz+ HF 8 GB DDR5 Ubuntu 24.04 Docker EMQX Cap + BBR Queue Vultr HF 8GB ($48/mo)
V2 + DEX Gateway + Dashboard 6 Dedicated VDS 16 GB DDR5 Ubuntu 24.04 Docker cpuset Pin + Node MaxOld UltaHost VDS 16GB / Vultr HF 16GB
Multi-Venue Desk (20+ Bots) 8–12 Dedicated VDS 32 GB ECC Ubuntu 24.04 Tuned NIC 16MB Socket Buffers + VDS UltaHost VDS 32GB ($58/mo)

BotFoundry Unattended Supervisor Snippet (BP-05 // HB-MM)

BotFoundry memory breakdown for Hummingbot V2 Python Cython loops, EMQX broker, and Node.js DEX Gateway
BotFoundry memory breakdown for Hummingbot V2 Python Cython loops, EMQX broker, and Node.js DEX Gateway
sysctl.conf — BotFoundry Kernel TCP BBR & Idle-Window Guard for Orderbook Sockets
# /etc/sysctl.d/99-botfoundry-hummingbot.conf
net.core.default_qdisc = fq
net.ipv4.tcp_congestion_control = bbr
net.ipv4.tcp_fastopen = 3
net.ipv4.tcp_slow_start_after_idle = 0
net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
  1. 1. Disabling tcp_slow_start_after_idle in BotFoundry Market-Making Kernel Profiles

    During quiet market intervals, default Linux kernels shrink the TCP congestion window on idle HTTP/2 keep-alive connections. Setting net.ipv4.tcp_slow_start_after_idle = 0 ensures burst cancel-replace payloads transmit immediately at full socket window capacity.

  2. 2. Why BotFoundry Adds +3.5 GB RAM Overhead for Hummingbot V2 + DEX Gateway Stacks

    Adding the TypeScript Hummingbot Gateway container (EVM/Solana SDKs), EMQX message broker, and Streamlit UI introduces four separate runtimes (Python, Erlang, Node.js, Postgres/SQLite) — making 8 GB tight and 16 GB DDR5 our clean operational baseline.

  3. 3. CPU Core Pinning (cpuset_cpus) Across Multi-Bot VDS Nodes on BotFoundry

    Pinning each Hummingbot Docker container to dedicated vCPU threads on a 6-core or 8-core UltaHost VDS prevents Python garbage collection in one strategy from stalling Cython orderbook parsing in another.

BotFoundry Troubleshooting & Sizing FAQ (BP-05 // HB-MM)

Why does BotFoundry weight 3.5GHz+ clock speed heavily for Hummingbot instances?

Each Hummingbot instance processes L2 orderbook diffs on a single-threaded asyncio/Cython event loop, so higher per-core clock frequency directly accelerates local state updates.

How does BotFoundry harden wallet keystores on unattended DEX Gateway servers?

Encrypt Gateway keystores with a strong passphrase, fund isolated hot wallets with capped per-bot capital, disable SSH password login (Ed25519 keys only), and block all inbound ports via UFW.

Can Hummingbot V2 Dashboard and live bots share one 8 GB VPS under BotFoundry rules?

Yes for up to 3–4 CEX-only bots without heavy historical backtesting; if you add DEX Gateway connectors or run 8+ strategies, step up to 16 GB RAM.

Related BotFoundry Unattended Sizing Blueprints

Vultr (BP-05 BotFoundry) From $6.00/mo
Inspect Specs on BotFoundry →