Running Bookmap on a VPS Without Losing the Heatmap
Traders try Bookmap on a generic VPS, watch the heatmap turn into a slideshow over RDP, and conclude order-flow platforms can't be hosted remotely. The conclusion is wrong — but it takes the right hardware and the right remote-session setup to prove it. Here is what Bookmap actually demands, and how to configure a server that delivers it.
Why Bookmap Is Heavier Than Other Platforms
Most charting platforms draw a new bar every few seconds. Bookmap repaints a scrolling liquidity surface on every book update — and with full-depth futures data, that can be thousands of updates per second per instrument. Subscribe to MBO data and the message rate climbs further, because you are now tracking individual orders rather than aggregated levels. All of that lands on CPU as rendering and bookkeeping work that runs on a small number of threads.
This is why single-core speed is the spec that matters. Our Ryzen 9950X cores are among the fastest single-thread CPUs available in hosting, which is the difference between a heatmap that flows and one that hitches when the book gets busy — exactly the moments order-flow traders care about most.
The Remote Session Is Half the Battle
A perfectly smooth heatmap on the server is worthless if the RDP session compresses it into smears. Standard remote desktop treats the screen as a mostly-static document and falls apart on continuously-animating surfaces. Our GPU-accelerated RDP pipeline encodes the session as a video stream instead, which is precisely what a scrolling heatmap needs — high, steady frame rates with readable detail.
Client-side settings matter too: RDP clients often cap frame rates by default, and an underpowered viewing device can bottleneck a healthy server. Our frame-rate optimization guide below covers the registry and client settings; five minutes of tuning is usually the difference between 'unusable' and 'indistinguishable from local'.
Data Feeds, Locations, and Plan Sizing
For CME futures, Bookmap's depth and MBO data typically arrives through Rithmic or dxFeed, whose infrastructure sits in the Chicago area — so our Chicago servers at 427 S La Salle keep the highest-volume connection in your stack short and stable. Crypto traders using the Binance connector are latency-flexible; any location works, so choose by where you'll RDP from.
Sizing: Bookmap's own requirements are real, not marketing. One or two instruments with standard depth run on Momentum ($85/mo, 8 cores, 20GB DDR5) — treat that as the practical floor rather than Swing, because heatmap history plus a data connection eats the smaller plan's RAM. MBO subscriptions, Multibook, or several instruments belong on Flow ($175/mo, 16 cores, 40GB, 300GB NVMe Gen5). Recording depth data for later replay is disk-hungry; NVMe Gen5 storage keeps both recording and replay fast.