Tradovate CQG Feed Throttled to ~2 Updates/Sec
The DOM redraws in chunks and Time & Sales prints arrive bundled during a fast move. Here's the two-layer reason, what's fixed upstream, and what you can actually tune.
You're watching ES or NQ rip through a news spike, and the tape stutters. The DOM redraws in chunks, the Time & Sales prints arrive bundled, and the whole feed feels like a couple of snapshots a second instead of every tick. Before you reinstall the app or blame your machine, here's the thing worth knowing: Tradovate's market data comes from CQG, and CQG nets its feed down to roughly two updates a second on the tape and depth pulse. That coarse cadence reaches every platform CQG supplies, it's a data-vendor behavior, not a bug on your desk. There's a second layer on top that you can influence, and that's where the fixable part lives. Let's separate the two so you know what to touch and what to accept.
Quick Checklist for a Throttled Tradovate Feed
- Know it's the feed, not your account. A steady ~2-per-second pulse in fast markets is CQG conflation, shared by every CQG-fed platform, nothing to fix on your side.
- Confirm your fills are still accurate. Orders match at the exchange, not against the on-screen tape. A coarse feed is a read problem, not a broken router.
- Clear local load. Check Task Manager; a maxed-out CPU or memory triggers Tradovate's own extra throttling on top of the feed.
- Stabilize your connection. A slow or unstable network makes the platform throttle your feed below the baseline. Wired beats Wi-Fi.
- Confirm your data is live, not delayed. Ten-minute delayed data (orange symbols) is a subscription problem, not throttling, different fix.
- Escalate only the right cases. Report data that's far worse than ~2 per second under calm conditions, or delayed data on a prop account (your firm controls that).
What “~2 Updates a Second” Actually Means
The number that trips people up is the pulse: the tape and depth of market refresh only about twice a second, not tick-by-tick. That's conflation. Instead of streaming every individual trade and quote change, the feed collapses whatever happened in the last interval into a single snapshot and sends the most recent state, discarding the intermediate steps. In a slow market you'd never notice, two updates a second is plenty when price barely moves. In a fast market, dozens of real events pile up between pulses and arrive bundled, so you see fewer, chunkier updates exactly when the action is thickest.
This matters because a conflated feed is a coarse picture of the market, not a broken one. Your fills still match at the exchange off live prices; the throttling lives in how often the display refreshes, not in the execution path. So a scalper hand-reading the ladder feels this hard, while a trader working off bars or signals barely registers it. Keep that split in mind, it decides which fixes below are worth your time.
Where the Throttling Comes From: Two Layers
There are two separate throttles stacked on your feed, and telling them apart is the whole game.
Layer 1: CQG feed conflation (the part you can't change)
CQG is the market-data provider behind Tradovate, and its consolidated feed is netted down to roughly two updates a second on the DOM and Time & Sales pulse. That's an upstream design choice at the data vendor, the same conflated cadence shows up on other CQG-fed platforms too, which is the tell that it isn't a Tradovate-only glitch or a problem with your setup. There is no user-facing control anywhere in Tradovate that raises this base cadence, because the limit isn't set in Tradovate. If your feed is holding a steady ~2-per-second pulse, that's the feed working as designed, and no amount of local tuning pushes it faster.
Layer 2: Tradovate's dynamic throttling (the part you can)
On top of the base feed, Tradovate can throttle your data further when it thinks you can't keep up. If the client application is performing poorly, or your network is slow, the platform starts bundling responses more aggressively, combining data for multiple symbols into the same message and discarding pending or out-of-date data in favor of the latest. Quotes, the DOM, and chart updates can all be affected. This is the layer you actually control: when a starved CPU or a shaky connection triggers it, you drop below the baseline feed and everything feels doubly sluggish. Clear those local causes and you at least get the full feed CQG is sending, instead of a throttled-down version of it.
Top Causes of Extra Feed Lag in 2026
Layer 1 is fixed. These are the Layer-2 triggers that drag you below even the baseline feed.
1. Local CPU or memory overload
When the feed gets choppier the longer you run, or clears after a restart, your own machine is usually the culprit. A stack of charts, several DOMs, indicators, and other trading apps can peg the platform's CPU and memory, and a starved client is exactly the condition that trips Tradovate's dynamic throttling. The first diagnostic is Task Manager: if the app or browser tab is near 100% CPU or memory, you've found the extra lag.
2. Slow or unstable network
The feed streams live, so a slow or flaky connection is another direct trigger for the platform to throttle your data down. Wi-Fi drops, VPN routing, and a saturated home network all interrupt the stream and read as bundled, catch-up updates. A drifting system clock compounds it, since Tradovate's real-time services are time-sensitive. A wired connection and a synced clock take both off the table.
3. Delayed data mistaken for throttling
This one's a category error. If your symbols show in orange or your data runs ten minutes behind, that's not throttling at all, it's a missing live market-data subscription. Delayed data is old; a throttled feed is coarse but current. They look vaguely similar at a glance but have completely different fixes, so confirm which one you're actually looking at before you troubleshoot.
How to Reduce Extra Feed Lag: Step-by-Step
Clear local platform load
Free up resources so Tradovate stops throttling you below the baseline feed.
Check Task Manager
Open Task Manager (Ctrl+Shift+Esc on Windows; Activity Monitor on macOS) and check the CPU and memory used by the Tradovate app or your browser tab. Note whether either is near 100%.
Close unused charts and DOMs
In Tradovate, close every chart, DOM, and panel you aren't actively trading. Each open module consumes resources and adds to the load.
Trim instruments and panels
Trim the number of instruments and simultaneous DOMs to only what the current session needs.
Close competing apps
Close other heavy apps competing for CPU and RAM, then watch whether the tape and ladder loosen up.
Stabilize your network and clock
Give the live stream a clean pipe so the platform doesn't throttle it.
Switch to wired Ethernet
Switch from Wi-Fi to a wired Ethernet connection where you can, and disable any VPN routing your trading traffic.
Sync your clock
On Windows, turn on Set time automatically, then click Sync now (Settings → Time & language → Date & time) so the system clock matches network time.
Free up bandwidth
Close background downloads and streams that eat your bandwidth while you trade.
Confirm your data is live, not delayed
Rule out the delayed-data trap before you judge the update rate.
Check the symbol color
Check whether your symbols display in the normal color or in orange, orange signals delayed, not live, data. Confirm the exact colour and indicator in your current build, as the styling shifts between platform updates.
Verify your data subscription
Open Tradovate's market-data settings and verify you hold an active real-time subscription for the exchange you're trading (for CME futures, that's the live CME data entitlement).
Contact your firm if needed
On a personal account you subscribe yourself; on a prop or evaluation account the firm enables your data, so contact the firm if it's missing. Data entitlements and rules vary by firm and account size, check your firm's current rules.
Reset, then escalate only the right cases
When you've cleared your side and something's still off, reset and report.
Reset the connection
On the web platform, refresh with F5; on the desktop app, fully close and reopen it to rebuild the data connection. Make sure you're on the latest build.
Judge against the baseline
Judge what's left against the baseline. A steady ~2-per-second pulse in fast markets is normal CQG conflation, nothing to escalate.
Contact support if it's still worse
Contact support (or your prop firm, for evaluation accounts) only if the feed is far worse than that under calm conditions, if it stays coarse after you've cleared load and network, or if your data is flat-out delayed. Send the time, instrument, and a screenshot.
Throttled Feed vs. Other Data Problems
| Symptom | What it means | Fix |
|---|---|---|
| Steady ~2 updates/sec on tape and DOM | CQG feed conflation (baseline cadence) | No user setting changes it; accept it or trade off signals instead of hand-reading |
| Feed drops below baseline, worse the longer you run | Tradovate dynamic throttling from local overload | Close extra charts/DOMs; check Task Manager; restart the app |
| Bundled, catch-up updates with freezes | Slow or unstable network / clock drift | Use wired Ethernet; enable “Set time automatically” and sync now |
| Feed coarsens only during volatile bursts | Conflation collapsing a flood of ticks into one snapshot | Expected behavior; it snaps back once the surge passes |
| Data is 10 minutes old / orange symbols | No live market-data subscription (delayed, not throttled) | Add the real-time subscription; on a prop account, ask the firm |
| Coarse feed across every CQG platform at once | Upstream data-vendor behavior, not Tradovate-specific | Nothing to change locally; it's shared by all CQG-fed platforms |
Stop Betting Your Entry on a Coarse Feed
If your edge depends on eyeballing a tape that pulses a couple of times a second in a market moving many times a second, the tape is the wrong thing to bet on. PickMyTrade lets your strategy act on the signal instead of on whatever a conflated feed happens to show:
- Signal-based execution, orders fire from your TradingView strategy the instant your condition triggers, not when a coarse tape finally catches up.
- Server-side routing, alerts route to Tradovate from PickMyTrade's servers, so a maxed-out local machine (the thing that trips Tradovate's extra throttling) doesn't gate your entries and exits.
- Rate-limit-safe order flow, order routing is spaced sensibly so nothing bounces off Tradovate's request limits.
- Multi-account sync, the same automated entry and exit mirror across several Tradovate accounts at once, no per-tick clicking required.
Trade the Signal, Not the Tape
Automate your entries so a couple of chunky feed updates a second never costs you the fill.
Start Your Free 5-Day TrialFrequently Asked Questions
No. It's the conflated cadence of the CQG market-data feed that Tradovate is built on. CQG nets down its tape and depth pulse to roughly two updates a second, and that same coarse feed reaches every platform CQG supplies, so it's a data-vendor characteristic, not a fault on your machine or your account.
Usually not. Orders match at the exchange, not against the picture on your screen. A coarse ~2-per-second feed makes the tape and ladder harder to read in fast conditions, but the execution engine still works off live exchange prices. The throttling is a display and read problem, not a broken order router.
There's no user setting that raises the CQG feed's base cadence, that pulse is fixed upstream. What you can control is the second layer: Tradovate applies its own dynamic throttling when your client app is bogged down or your network is slow. Clearing local load and stabilizing your connection removes that extra throttle so you at least get the full ~2-per-second feed instead of something worse.
Conflation collapses a burst of ticks into a single snapshot and keeps only the most recent value. When price is ripping, dozens of real trades and quote changes happen between each ~half-second pulse, so they arrive bundled, you see fewer, chunkier updates precisely when the most is happening.
It removes Tradovate's dynamic throttle layer, so it stops your feed being throttled below the baseline. It won't push you past the CQG feed's roughly two-per-second ceiling, though, that limit lives at the data vendor, not on your desk.
No, that's a different issue. A 10-minute delay (often shown with orange symbol names) means you don't have a live real-time market-data subscription, the data is old, not just coarse. Throttling is about how often live data updates; delay is about whether it's live at all. Fix the subscription first, then judge the update rate.
Escalate if the feed is far worse than a steady ~2-per-second pulse under calm conditions, if it stays coarse after you've cleared local load and your connection, or if your data is delayed rather than throttled. On a prop or evaluation account the firm controls your market data, so contact them, entitlements and rules vary by firm and account size, so check your firm's current rules.
This guide is for educational and informational purposes only and is not financial, investment, or trading advice. Trading futures and other leveraged products carries a substantial risk of loss and is not suitable for every investor. PickMyTrade is an independent third-party automation platform and is not affiliated with, endorsed by, or sponsored by Tradovate, Inc. or Bookmap. All related names, logos, and trademarks are the property of their respective owners. Platform features and steps change over time, so always confirm the current process in the official platform documentation before acting.