1. Describe what feels slow
Record a specific action: opening a saved workspace, loading a chart, switching instruments, or moving around a chart. Note the instrument, contract month, connection, time of day, chart count, indicators, and whether the issue repeats.
Keep chart responsiveness separate from market data delay and order execution. A chart that takes time to redraw is not evidence that orders are delayed.
2. Preserve your working setup
Save your workspace and use the platform’s documented backup process before experimenting. Work from a copy, outside active trading, with simulation selected. Check the selected account before every order-related test.
Do not delete platform data, reinstall software, or disable security tools as a first diagnostic step. If the platform is unstable or an order is uncertain, use official platform or broker support.
3. Establish a simple baseline
Start with a separate, minimal workspace containing a single chart of the same instrument and connection. Keep its chart type, historical lookback, and session settings documented. Compare the action that originally felt slow.
A simpler workspace can help isolate workload differences. A better result is a diagnostic clue, not proof that a particular feature is defective.
4. Change one source of workload
- Historical data: check whether each chart needs its current lookback. Test a smaller range on the copy.
- Charts: compare the minimal workspace with your normal chart collection. Avoid assuming a hidden window has no workload.
- Indicators and add-ons: add them back individually and repeat the same observation. Follow the vendor’s guidance.
- Calculation settings: understand any indicator’s calculation behaviour before altering it. Changes can affect signals, not just responsiveness.
- Computer activity: observe CPU, memory, disk, and network use with normal operating-system tools. Check for unrelated intensive tasks.
Avoid universal chart limits, hardware promises, and configuration recipes. A useful setting for one strategy can change another strategy’s behaviour.
5. Keep a short comparison log
| Record | Example of what to write |
|---|---|
| Observation | Time from opening the workspace until charts are usable. |
| Conditions | Version, connection, instrument, session, and computer workload. |
| One change | Reduced historical lookback on the test chart. |
| Outcome | Measured result, whether it repeats, and any changed behaviour. |
| Decision | Keep the change, restore the original, or ask support. |
Repeat under comparable conditions. Market activity and data caching can affect observations, so avoid treating one faster load as a reliable benchmark.
6. Escalate with useful evidence
If the issue persists in a simple workspace, contact official support with the reproduction steps and your comparison log. Review the official help guide for version-specific performance and backup instructions.
NinjaTrader 8 official documentation ↗
This workflow has not been benchmarked by NinjaProTrading. It makes no claim about a percentage improvement, execution speed, or trading results.