alBuys vs OnMarketData

[ct]

I have an indicator I did a long time ago which used BuySellVolume at the time as a base and it used theOnMarketData method.

I just looked at my current ninja base BuySellVolume indicator source code and see it uses a different method of GetCurrentAsk and GetCurrentBid then using "Volume".

Is there some advantage or pros or cons using the GetCurrentAsk method over OnMarketData? What I have works fine but didn't know if this new method is better in some way. If ninja is using this method I am guessing it is better for some reason.

Can you enlighten me?

[ct]

I changed my indicator to the new method using GetCurrentAsk and seems like it's faster plus it agrees exactly to the VOL indicator where as before I used to get small discrepancies on occasion.

[NinjaTrader_Joydeep]

Hello ct,
Thanks for your note.

OnBarUpdate and OnMarketData runs on separate thread and thus the data may differ. Please refer to our help guide to know more.

4. With NinjaTrader being multi-threaded, you should not rely on any particular sequence of events like OnMarketData() always being called before OnBarUpdate() or vice versa.

http://www.ninjatrader.com/support/helpGuides/nt7/index.html?onmarketdata.htm

If you are comparing/matching the bid/ask price with the last traded price in the OnBarUpdate event then please use GetCurrentBid/GetCurrentAsk functions.

[ct]

Joy


Thanks for the reply.

Appreciate the separate threads and event based scenario. It there any performance considerations?

[NinjaTrader_Joydeep]

Hello ct,
Yes, OnMarketData is the raw data stream and can be CPU intensive depending on your code.

This is a real-time data stream and can be CPU intensive if your program code is compute intensive (not optimal)

http://www.ninjatrader.com/support/h...marketdata.htm