The Real Culprit Behind CPU 100%: A Missing `ok` in Go and the Resulting Busy-Loop
Post-mortem of an intermittent CPU 100% — a Go select-read on a channel without ok, zero-values flood the loop after close. Includes SIGUSR1 dump trick and repo-wide sweep.
Related Content
Tags
Perpetual Funding Rates: A Bot Trader's Practical Primer
Bot-first P&L: where funding lands in equity, how it stacks with turnover and inventory, and risk-off triggers—linking the basics article.
Turning Your Trading Bot Into "Something the AI Can Call": MCP in a Quant System
MCP standardizes tool description, invocation and return shape. A practical guide to splitting meta / read / write tools, auth, description craft, tool-count limits and testing.
Related Posts
QuantMesh Core Implementation: Architecture of a High-Performance Grid Trading System
Layered design, concurrency, state management, IExchange abstraction, and risk controls—technical deep dive into QuantMesh after large-scale live trading volume.
Picking an LLM Provider for Your Trading Bot: Gemini vs OpenAI vs Claude vs DashScope vs Kimi vs DeepSeek
Wiring an LLM into an automated trading system: route by task, abstract the provider, scrub secrets end-to-end. A field-tested guide across seven upstreams.
Turning Your Trading Bot Into "Something the AI Can Call": MCP in a Quant System
MCP standardizes tool description, invocation and return shape. A practical guide to splitting meta / read / write tools, auth, description craft, tool-count limits and testing.