NexusFi: Find Your Edge


Home Menu

 





NT7 system lagging with multiple windows


Discussion in NinjaTrader

Updated
      Top Posters
    1. looks_one Seanbeshore1 with 8 posts (0 thanks)
    2. looks_two Zondor with 5 posts (9 thanks)
    3. looks_3 sam028 with 2 posts (0 thanks)
    4. looks_4 cory with 1 posts (0 thanks)
      Best Posters
    1. looks_one Fat Tails with 9 thanks per post
    2. looks_two traderadam with 4 thanks per post
    3. looks_3 Zondor with 1.8 thanks per post
    4. looks_4 wshi88 with 1 thanks per post
    1. trending_up 6,833 views
    2. thumb_up 23 thanks given
    3. group 12 followers
    1. forum 24 posts
    2. attach_file 1 attachments




 
Search this Thread

NT7 system lagging with multiple windows

  #11 (permalink)
 
Fat Tails's Avatar
 Fat Tails 
Berlin, Europe
Market Wizard
 
Experience: Advanced
Platform: NinjaTrader, MultiCharts
Broker: Interactive Brokers
Trading: Keyboard
Posts: 9,888 since Mar 2010
Thanks Given: 4,242
Thanks Received: 27,102


Seanbeshore1 View Post
NinjaTrader support was of no help to me as they are not familiar with indicators supplied by this site. I started a thread here in hopes of getting a different perspective. NT support simply told me to remove indicators that may be causing the issue....however its hard to determine what combination of indicators is causing the issue. The indicators when used on there own do not cause any lagging issues.


Usually the indicators do not interfere. This means that the CPU load caused by a specific indicator is the same, whether it is used alone or in combination with other indicators. Of course several badly coded indicators can add up to exceed the threshold.

There are a few things that you can do to reduce CPU load

- first use all your indicator with CalculateOnBarClose = true
- second do not change the display updated interval to a lower value than 0.5 sec

You may also post the source code of the indicators - or in case that you have downloaded them from this forum, post a link to the source file - and we should be able to tell you which of the indicators cause the CPU load. A general statement does not help. We need to go into details.


You can further conduct individual tests for each indicator to determine the CPU load as follows:

-> download Microsoft Process Explorer
-> download one week of replay data for ES 12-15 (it is free)
-> open a virgin chart for ES 12-15
-> add the indicator to the chart and set it to CalculateOnBarClose = false (maximum damage)
-> start market replay at maximum speed (x 500)
-> open Process Explorer and watch the CPU load for all kernels of your processor

When played at speed x 500, the regular session for ES should take about 50 seconds. If it takes a few minutes to complete you know that you will be running into problems.

Reply With Quote

Can you help answer these questions
from other members on NexusFi?
The space time continuum and the dynamics of a financial …
Emini and Emicro Index
Futures True Range Report
The Elite Circle
Are there any eval firms that allow you to sink to your …
Traders Hideout
Exit Strategy
NinjaTrader
My NT8 Volume Profile Split by Asian/Euro/Open
NinjaTrader
 
  #12 (permalink)
 traderadam 
London
 
Experience: Intermediate
Platform: Ninja, Sierra, Jigsaw
Trading: ES
Posts: 14 since Jun 2014
Thanks Given: 8
Thanks Received: 55

I to use 4 screens and look at a lot of data, NT7 is designed to stuff all processing through 1 core and is very laggy. There are a few things I have learnt that offset this and just about make NT7 well half usable...roll on NT8.....or is that just a myth

I got this info from the Jigsaw site where you will find in detail how to do it all in the forum (Petes a saint):

You have to minimise disk writes so as not to bombard disk with unimportant stuff.

1 - If you dont need market reply data, turn it off
2 - Disable search indexing (youtube video)
3 - Download Process hacker:

Go to Processes tab

A - Right click Ninja, Affinity, deselect, select 1 core (I the 2nd)

B - Right click Ninja, Priority, High

C - Right click Ninja, I/O Priority, High

Once you have done this, get task manager up and you will be able to see Ninja raping the chosen core and you will be giving it the best chance to not let you down by clogging your disk up.

You will have to do this every time you start Ninja, but it only takes 30 seconds. Hope this helps

Reply With Quote
Thanked by:
  #13 (permalink)
tmytrade
Kuala Lumpur Malaysia
 
Posts: 2 since Feb 2015
Thanks Given: 1
Thanks Received: 0



traderadam View Post
I to use 4 screens and look at a lot of data, NT7 is designed to stuff all processing through 1 core and is very laggy. There are a few things I have learnt that offset this and just about make NT7 well half usable...roll on NT8.....or is that just a myth

I got this info from the Jigsaw site where you will find in detail how to do it all in the forum (Petes a saint):

You have to minimise disk writes so as not to bombard disk with unimportant stuff.

1 - If you dont need market reply data, turn it off
2 - Disable search indexing (youtube video)
3 - Download Process hacker:

Go to Processes tab

A - Right click Ninja, Affinity, deselect, select 1 core (I the 2nd)

B - Right click Ninja, Priority, High

C - Right click Ninja, I/O Priority, High

Once you have done this, get task manager up and you will be able to see Ninja raping the chosen core and you will be giving it the best chance to not let you down by clogging your disk up.

You will have to do this every time you start Ninja, but it only takes 30 seconds. Hope this helps

Thanks for this detail...been struggling with NT7 for a while with it's speed, maybe it's because I only have 8GB of RAM...??? Gotta try this out this week!

Reply With Quote
  #14 (permalink)
 Seanbeshore1 
orlando, fl, USA
 
Experience: Intermediate
Platform: Ninjatrader
Trading: Crude Oil
Posts: 16 since May 2015
Thanks Given: 0
Thanks Received: 2

Thanks FAT TAILS for the insight. I have narrowed it down to 3 indicators I've imported from the forum. Each causes chart lag on their own. I've changed system parameters as outlined and still have chart lag. I will most likely need to hire someone to have these three indicators recoded. The VolStop indicator has a known issue of not being able to save default colors.

BMT WAVE


mkSupDemZones


VolumeStopNT7

Best,

Sean
Started this thread Reply With Quote
  #15 (permalink)
 
matthew28's Avatar
 matthew28 
United Kingdom
 
Experience: Beginner
Platform: Bookmap
Broker: Stage 5, Rithmic
Trading: US Equity Index Futures
Posts: 1,250 since Sep 2013
Thanks Given: 3,500
Thanks Received: 2,532

.

Reply With Quote
  #16 (permalink)
 
cory's Avatar
 cory 
virginia
 
Experience: Intermediate
Platform: ninja
Trading: NQ
Posts: 6,098 since Jun 2009
Thanks Given: 877
Thanks Received: 8,090

limit number of load days to 3 see if that help

Reply With Quote
  #17 (permalink)
 Seanbeshore1 
orlando, fl, USA
 
Experience: Intermediate
Platform: Ninjatrader
Trading: Crude Oil
Posts: 16 since May 2015
Thanks Given: 0
Thanks Received: 2

Cory, My indicators require at least 14 days of history...thanks for the input.

Best,

Sean
Started this thread Reply With Quote
  #18 (permalink)
 
ratfink's Avatar
 ratfink 
Birmingham UK
Market Wizard
 
Experience: Intermediate
Platform: NinjaTrader
Broker: TST/Rithmic
Trading: YM/Gold
Posts: 3,633 since Dec 2012
Thanks Given: 17,423
Thanks Received: 8,425


Seanbeshore1 View Post
Cory, My indicators require at least 14 days of history...thanks for the input.

You could run his in a chart with 3 days and yours in a chart with 14 days.

Travel Well
Visit my NexusFi Trade Journal Reply With Quote
  #19 (permalink)
 
Zondor's Avatar
 Zondor 
Portland Oregon, United States
 
Experience: Beginner
Platform: Ninjatrader®
Broker: CQG, Kinetick
Trading: Gameplay Klownbine® Trading of Globex
Posts: 1,333 since Jul 2009
Thanks Given: 1,246
Thanks Received: 2,731

The BMT wave indicator was fixed in 2010 (by me), so nothing to be done there. The swing indicator, if running COBC false, does not have anything to prevent processing of redundant intrabar ticks (same price as preceding tick). It's a total waste to process redundant intrabar updates. Generally at least 70% of intrabar ticks are redundant. Best bet would be to make sure swing indicator is running on COBC true.

Be careful about setting Ninjatrader priority to high, can bring your PC to a standstill.

Your strategy will probably work MUCH better in NT8 with its multi core multi threading.

Don't forget about the Ninjatrader setup hints in Post #7.

"If we don't loosen up some money, this sucker is going down." -GW Bush, 2008
“Lack of proof that something is true does not prove that it is not true - when you want to believe.” -Humpty Dumpty, 2014
“The greatest shortcoming of the human race is our inability to understand the exponential function.”
Prof. Albert Bartlett
Follow me on Twitter Visit my NexusFi Trade Journal Reply With Quote
Thanked by:
  #20 (permalink)
 Seanbeshore1 
orlando, fl, USA
 
Experience: Intermediate
Platform: Ninjatrader
Trading: Crude Oil
Posts: 16 since May 2015
Thanks Given: 0
Thanks Received: 2


Many thanks, Zondor. Will these indicators, among others, be easily converted to NT8? Love your quotes BTW.

Best,

Sean
Started this thread Reply With Quote




Last Updated on November 12, 2015


© 2024 NexusFi™, s.a., All Rights Reserved.
Av Ricardo J. Alfaro, Century Tower, Panama City, Panama, Ph: +507 833-9432 (Panama and Intl), +1 888-312-3001 (USA and Canada)
All information is for educational use only and is not investment advice. There is a substantial risk of loss in trading commodity futures, stocks, options and foreign exchange products. Past performance is not indicative of future results.
About Us - Contact Us - Site Rules, Acceptable Use, and Terms and Conditions - Privacy Policy - Downloads - Top
no new posts