NinjaTrader 8 Slow or Lagging? Find the Cause Before You Change Anything

When NinjaTrader 8 feels slow, the cause is usually one of five things: the charts themselves (rendering), indicators and strategies doing too much work (NinjaScript), too much historical data (days loaded, Tick Replay), a PC that is short on resources, or a connection problem that only looks like platform lag. Spend five minutes finding which one before you change any settings. Each has a different fix, and a VPS fixes only some of them.

Menu names below are for NinjaTrader 8.1.x.x (checked against NinjaTrader’s help guide, October 2026). Before 8.1.5, Tools › Settings was called Tools › Options.

Which kind of slow is it?

Match what you see to a row, then go to that section.

Measure first: a five-minute check

1. Look at the whole PC. Press Ctrl+Shift+Esc to open Windows Task Manager, then sort the Processes tab by CPU and then by Memory. If something other than NinjaTrader is at the top (a sync client, a browser, an antivirus scan), start there.
2. Look inside NinjaTrader. In the Control Center, go to New › NinjaScript Output, right-click inside the Output window and choose NinjaScript Utilization Monitor. It adds up the time each indicator and strategy uses from the moment you open it, so leave it running for 2 to 5 minutes in a busy market. Focus on the scripts at the top; small totals don’t matter.
3. Test in Safe Mode. Exit NinjaTrader, then hold Ctrl while you start it and keep holding until the Control Center appears (or choose NinjaTrader (Safe Mode) from the Start menu). Check Help › About to confirm. Safe Mode does not load workspaces, does not connect at startup and does not load custom assemblies (add-ons), so connect by hand.
4. Compare. Open a chart or two without your custom indicators, then open your workspace. If it runs well in Safe Mode, an installed add-on that Safe Mode skipped is the likely cause. If it is still slow, the workspace itself is too heavy for this PC, often because of the scripts on it. Do not save the workspace while in Safe Mode.

If even one plain chart is slow in Safe Mode, go straight to the PC and connection sections below.

Charts and rendering

These come from NinjaTrader’s own performance tips, with what each one costs you.

• Close workspaces you aren’t using with Workspaces › Close. A workspace that is open but not in view still uses resources. Save it first, because workspaces do not auto-save.
• Close extra charts, SuperDOMs, Market Analyzers and tabs. NinjaTrader’s own example: 200 charts use more processing power than 20.
• Use fewer Global crosshairs. A Global crosshair (Ctrl+G) is linked across every chart where it is enabled, so there is more to draw as the mouse moves. Set charts that don’t need it to Local (Ctrl+Q). Trade-off: those charts stop following other charts’ crosshairs.
• Turn on Draw cursor only. In Chart Properties (Ctrl+T), expand Lines › Crosshair and check Draw cursor only. NinjaTrader recommends it for PCs with less powerful graphics cards. Trade-off: the full crosshair lines are no longer drawn across the chart.
• Remove drawing objects you no longer need. They pile up, and each one has to be drawn.
• Use the dedicated graphics card on PCs that have two, common on laptops. In Windows 11, Settings › System › Display › Graphics lets you set NinjaTrader to high performance.

NinjaScript: indicators and strategies

If the platform keeps up when the market is quiet and falls behind at the open or on news, look at the work done per tick. More trades per second means every script that runs on each tick runs that many more times.

• Check Calculate on each indicator. Open the Indicators window (Ctrl+I), select an indicator and look at Calculate. NinjaTrader recommends On price change or On bar close, and says there is no benefit to On each tick unless the indicator deals with volume or tick counting. Trade-off: On bar close updates once per bar, and On price change ignores ticks that don’t change the price. Strategies have the same setting.
• Remove indicators you don’t use, including ones on Market Analyzer columns and SuperDOMs.
• Read the Utilization Monitor fairly. NinjaTrader’s documentation says a script at the top may not be coded as efficiently as it could be, or may be doing heavy calculations by design. Send the result to that script’s developer before you delete something you rely on.
• Spread instruments, not copies. NinjaTrader spreads its work across CPU cores, but a workspace built on one or two instruments can’t use that as well. NinjaTrader’s example: 30 charts of the same instrument perform worse than 30 charts of different instruments. Fewer windows on the same instrument helps.

Your data provider matters too: NinjaTrader notes that unfiltered tick data (every tick) puts a heavier processing load on the platform than throttled data.

Historical data: days loaded and Tick Replay

If charts take forever to load, or memory climbs as you add charts, look at how much history each chart pulls in.

• Load less history. Open the Data Series window (Ctrl+F) and lower the amount under Load data based on (Days, Bars or a custom range). NinjaTrader says this is especially effective on tick-based series. Do the same for indicator columns in the Market Analyzer. Trade-off: an indicator with a long lookback, like a 200-period average, needs at least that many bars loaded.
• Use Tick Replay only where it earns its cost. Tick Replay loads the bid, ask and last data behind each historical bar in exact sequence, and NinjaTrader warns that it uses more PC resources. It only helps indicators programmed for it: a simple pivot gains nothing, while a volume profile that depends on the order of trades does. To turn it off, uncheck Tick Replay on that series in the Data Series window. The checkbox only appears when Tools › Settings › Market data › Show Tick Replay is enabled. Trade-off: an indicator written for Tick Replay may calculate historical bars differently without it.
• Turn off market recording you don’t use. Under Tools › Settings › Market data, uncheck Enable market recording of playback if you don’t use the Playback connection. NinjaTrader also says to disable Record live data as historical if your provider supplies historical data. Trade-off: today’s session is not recorded for Playback.
• Connect on start up. For a connection you set up under Multi-provider, checking Connect on start up means your workspace loads once instead of twice (again when data downloads after you connect). Test the connection first: NinjaTrader warns that wrong credentials there can stop the platform from starting.
• Clear out simulation history you don’t need. Lots of simulated trades grow the database. Reset DB deletes historical orders and executions and keeps chart data and simulation accounts; our maintenance guide covers it.

The PC: CPU, memory, graphics and background work

NinjaTrader is not single-core. That is a common myth. NinjaTrader’s system requirements page says the platform uses all available CPU cores. The catch is the one above: NinjaTrader says a workspace built on one or two instruments benefits more from a higher clock speed.

NinjaTrader’s recommended specs, on Windows 11 or Windows Server 2016 or later (64-bit):

• Quad-core 64-bit processor, 2 GHz or faster
• 8 GB RAM
• DirectX 10 compatible graphics card
• SSD

NinjaTrader adds that you may need more or less depending on how you use it, and that extra memory directly helps strategy optimizations.

• High memory is not a diagnosis. NinjaTrader notes that high memory use may not be related to poor performance, because the system frees unused memory when it is needed rather than constantly. Watch whether slowdowns line up with memory, not the number alone.
• Exclude NinjaTrader from Windows Search indexing. NinjaTrader says indexing can put an extra burden on your processor. In Control Panel › Indexing Options › Modify, uncheck Documents\NinjaTrader 8 and the NinjaTrader 8 folder under Program Files.
• Keep NinjaTrader out of OneDrive. If OneDrive backs up your Documents folder, it is syncing Documents\NinjaTrader 8, where NinjaTrader keeps its database, logs and chart data, a recurring cause of crashes and missing files. Stop OneDrive backing up Documents, keep NinjaTrader 8 in a local Documents folder, then run NinjaTrader’s Repair (see our OneDrive guide).
• Close background apps you don’t need while you trade.
• Restart NinjaTrader daily. It is on NinjaTrader’s own list. Make sure it fully exits: 8.1.8 fixed a case where NinjaTrader could occasionally remain running after exit, one reason to stay current.

Late prices: the connection, or local processing?

If menus, scrolling and the crosshair respond normally but prices seem late, either the data reaches your PC late (the connection), or it arrives on time and your scripts can’t keep up (local processing). Safe Mode separates them: if prices are still late on one plain chart in Safe Mode, look at the connection, because chart settings won’t help.

• Use a wired connection. NinjaTrader notes that wireless and satellite connections can drop packets or have poor latency.
• If NinjaTrader is warning that market data is delayed, follow our market data delayed guide.

Do you need a VPS?

Measure first. A VPS (a Windows server you rent in a data center) helps with two things: the distance between you and the servers your data and orders go through, and a home PC that is too weak or unreliable. NinjaTrader itself suggests a VPS when a low-latency connection isn’t available to you.

A VPS does not fix an overloaded workspace. The same charts, Tick Replay series and On each tick indicators do the same work on a server. If the Safe Mode test or the Utilization Monitor points at your workspace, fix that first. Then compare the CPU, memory and graphics a VPS plan includes against the specs above.

Chart Studio: see what is loading your workspace (coming soon)

Our Chart Studio add-on, opening soon, includes free performance checks built for this job: seeing what is loading your workspace, before and after a change. It measures. It does not make NinjaTrader faster.

• A responsiveness check you can compare against your own baseline
• A processing lag monitor for chart and instrument queues, which shows local delay inside NinjaTrader rather than your provider’s latency, with an optional sound
• A memory monitor that samples every 5 minutes
• Workload counts per chart: data series, bars and indicators
• A 30-second performance timeline you can save as CSV
• Saved-workspace and chart-loading checks

The checks are in the free tier (a free account with this PC registered). Use them the way this article suggests: take a baseline, change one thing, and measure again.

Frequently asked questions

“It’s much slower today with only one chart. Where can I see what’s using resources?”

Use Windows Task Manager for the whole PC and the NinjaScript Utilization Monitor (New › NinjaScript Output, then right-click) for indicators and strategies. If both look normal, close any workspaces open in the background, then run the Safe Mode test.

“Will having two charts open slow Ninja down?”

Every chart adds some load, but NinjaTrader’s own example of a heavy load is 200 charts versus 20. With two charts, what is on them matters more: days loaded, Tick Replay and indicators set to On each tick.

“By 9:30 with all my add-ons loaded, NinjaTrader isn’t tradeable.”

The open is one of the busiest times of the day, so per-tick work peaks then. Open the Utilization Monitor before the open, read it a few minutes after, then run the Safe Mode test. If the workspace runs well without add-ons, take the Utilization Monitor result to the add-on’s developer.

“What PC specs do I need for 20-40 accounts?”

NinjaTrader doesn’t publish specs by account count. Start from its recommended spec (quad-core 2 GHz or faster, 8 GB RAM, SSD, DirectX 10 graphics), size up for the charts, SuperDOMs and strategies you keep open across those accounts, and measure your real workspace before you buy.

“Charts take forever to load.”

Lower Load data based on in the Data Series window, especially on tick-based charts, and turn off Tick Replay wherever no indicator needs it. If charts that used to load quickly suddenly don’t, our maintenance guide covers the chart data cache and other repair steps.

Is NinjaTrader single-core?

No. NinjaTrader’s requirements page says it uses all available CPU cores. Workspaces built on one or two instruments spread their work less well, so a higher clock speed helps there.

If NinjaTrader stops responding entirely instead of running slow, see NinjaTrader freezing or not responding. For cache, Reset DB and Safe Mode steps, see the NinjaTrader maintenance guide.