Hoping to get some wisdom from the indicator gurus here who have been in my shoes.
I'd like to have NT chart indicators set to "Calculate on bar close" = 'False' , so they keep up with the current bar of price action (not lagging one bar behind current price), but am worried it will over stress the one processor core NT uses.
The computer is new with a Quad core Xeon W3565 (3.2 ghz) - 12 RAM - 10K RPM 300 Hard Drive.
The minimum I could do per instrument traded is two charts with a total of 19 indicators and a superDOM.
Do you think that will run smoothly?
If needed I can just apply the real time setting to some of the indicators. While also cutting down the number of historical days loaded AND increase the chart refresh interval (sec) slightly on the higher time frame chart.
I trade SI, CL and 6E but only one at a time.
Do you think I could have the six charts up but only use the real time indicator setting on the two charts of the instrument being traded?
Thanks a million for the responses - I know it's something that can just be tested - but I haven't had any problems with NT and don't want to create them.
"Be right and sit tight." - Jesse Livermore
Last edited by whatnext; June 29th, 2011 at 01:35 AM.
If you use an indicator in CalculateOnBarClose = false mode, it will perform calculations with every incoming tick, and not just once, when the bar is completed.
You should avoid this, if you do not need the information.
My default workspace has 5 charts, and on each chart I have set some indicators to CalculateOnBarClose = false, because I want them to update in real-time. I have an old processor with a dual core, and I do not have problems so far.
This is what you can consider:
-> Only use indicators that are properly coded in a way that they can be updated without consuming 150% of the capacity of your CPU. Before using an indicator in CalculateOnBarClose = false mode you should either examine the code or test the indicator in real-time. Open a default chart and monitor CPU load without the indicator.
Then add the indicator 3 times with different settings to the chart, and monitor CPU load again
-> For monitoring CPU load download Process Explorer from the Microsoft website.
-> During the indicator test, the chart needs to be visible, if you cover the chart, this will reduce CPU load and this is not what you want during the test.
-> If you use indicators with custom plots, the plotting can consume CPU capacity as well. In this case try to increase the display update interval under chart properties to 0.5 sec. You do not need to have a new chart pciture 10 times per second.
-> Once you have tested your indicators individually, add all indicators that you want to use in CalculateOnBarClose = false mode to a default chart. Add some more of these charts and monitor CPU load.
Some indicators are awfully coded and cannot be run in CalculateOnBarClose = false mode.
The following 2 users say Thank You to Fat Tails for this post:
100 people on here must have dealt with the exact same thing and the input would still be very much appreciated to minimize the methodical testing.
The only helpful advice I can think of in exchange is that when ordering a workstation; only paying for 2 or three gb of factory ram, but then buying 12 gb (in 3 strips) of compatible Crucial or Kingston ECC to put in after, should save over $600...
A downside could be that the company gets pissed at what you are doing and will not inspect voltages as carefully. I ordered another workstation (Dell T3500) and noticed it shipped in 1/4 the time of their estimation.
Also on NT getting a 6 core CPU instead of a good 4 core isn't worth it because only one core is used.