NexusFi: Find Your Edge


Home Menu

 





NT7 Order Placement Timing


Discussion in NinjaTrader

Updated
    1. trending_up 1,508 views
    2. thumb_up 0 thanks given
    3. group 3 followers
    1. forum 1 posts
    2. attach_file 0 attachments




 
Search this Thread

NT7 Order Placement Timing

  #1 (permalink)
 
TexasTrader's Avatar
 TexasTrader 
Dallas, TX
 
Experience: Intermediate
Platform: NinjaTrader, MultiCharts, TradeStation
Broker: Mirus/Zen-Fire, TradeStation
Trading: Futures
Posts: 15 since Apr 2010
Thanks Given: 0
Thanks Received: 4

Hello BM and other forum members.

Question on NT7 and timing - I realize NT7 has 1 sec interval for historic data, and the chart can be refreshed up to every 100ms...

However what about automated strategies - at what interval does NT7 process & send orders? Is it as fast as the data is received, or internally does NT7 push data into a 1s interval for processing and placement of orders? Is there an inherent limitation to processing speed from C#?

I realize there are latencies like internet, distance to exchange, complexity of algos in strategy, etc, however assuming co-located at exchange and fast CPU w/ simple algo... What are the NT7/C# order processing & placement timing abilities?

Thanks.

Started this thread Reply With Quote

Can you help answer these questions
from other members on NexusFi?
REcommedations for programming help
Sierra Chart
ZombieSqueeze
Platforms and Indicators
Quantum physics & Trading dynamics
The Elite Circle
OrderFlow-Based Support/Resistance Levels
Emini and Emicro Index
NT7 Indicator Script Troubleshooting - Camarilla Pivots
NinjaTrader
 
Best Threads (Most Thanked)
in the last 7 days on NexusFi
Funded Trader platforms
32 thanks
Just another trading journal: PA, Wyckoff & Trends
23 thanks
Trading with Intuition
17 thanks
Self sabotage reframed
11 thanks
ApexTraderFunding.com experience and review
10 thanks
  #2 (permalink)
 choke35 
Germany
 
Experience: Intermediate
Platform: Other
Trading: ES, YM, 6E
Posts: 2,668 since Feb 2013
Thanks Given: 5,101
Thanks Received: 6,558

If you want to implement HFT, it's fairly safe to say, that co-location, tick update, lean implementation (pure binary code (no load-driving frameworks etc.), no unnecessary overhead during runtime, i.e. completely separate monitoring systems on separate data) and direct access to the order book are your most important (technical) bottlenecks.

Forget about tuning C# code pieces, especially if you have time-consuming stations like brokers in the game; not to mention the overhead you incur by using frameworks or standard libraries you might use. Surely, you will win some milliseconds by optimizing your own parts of the C# code, but that is bits and pieces compared to the other components.

Reply With Quote




Last Updated on November 12, 2013


© 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