Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I dont have SSD for my NT install: I use a ramdrive made up of DDR2 dimms. I still defragment. I realize with SSD there is the offset effect of wear leveling, but that is a concern of the SSD software itself and should be transparent to the operating system (much like a SMART hard drive remapping out bad sectors on a platter). Each time data is not contiguously stored, the OS must contend with pointers to data in other locations. It's not much overhead, but it's not zero. I also think having NT database file fragmented into hundreds of pieces could eventually lead to the disk structure starting to be prone to slowdown or crashing. Hopefully not, but who's to say it's perfect. For me, I backup the NT database with their backup tool each day and defrag & image at least weekly.
Can you help answer these questions from other members on NexusFi?
This post spurred me to relook at my datafeed: thanks!
Just using TT datafeed (Velocity is my broker) for the last two weeks and it looks stable even with some brisk market activity. I am fairly certain it is not filtered. I have some multiple charts for YM NQ 6ABCES .
I did use BarChart as my primary feed before. Still keep it for loading up historical data. I am setting up a machine just to record data for backtests so the BarChart feed will be diverted there for now.
I'd wanted to have NT/Zen-Fire just for my charting and another platform (TransActAT) for my trade execution. However, the responses I received from NinjaTrader and Zen-Fire was constraining me to an NT/Zen-Fire-based Broker, and which is against my plan to have a different Broker's platform for my trade execution.
So, please how did you have X_Trader for your trade execution and NT for your charting ? Do you have an NT-based Broker ? What data-feed do you use for your NT/X_Trader combination. For example, can I have NT/IQFeed just for my charting without the need to have an NT-based Broker ?
Working on my own Who would be interested in testing and providing feedback? VERY early stage (heck, I just design the connection window, after spending months on inner workings)
.NET 4.0, written in C#. Client/Server archtecture using SQL Server as backend - a "single user only" setup can run with SQL Express and starting a local server. The user interface uses WPF and is heavily optimized: every "work area" (window) works in it's own thread - although I do not cluster the area with hundreds of windows, one window per screen is assumed (with "controls" on the window representing charts etc.) VERY expandable in theory - the core application can not eve show charts, handle orders... it loads extensions for everything at the start (no worry, provided, but it means you can do top level stuff unlinke ninja).
I've been a NT uses for several years and yeah it has been difficult. In the past wth 6.5 I had alot of issues loading my charts and corrupted databases. NT support told me that it was due to my ISP. Well I have 2 ISP's and they problem was present with both. It's not a good way to start the trading day pulling your hair out just trying to get your charts up.
With backtesting 6.5 was terrible, I had tick tests that would take days, and then often crash before the end, upgrades never helped.
Now that NT7 is out I am seeing a definite change in support, for the better. I guess they are expecting problems, so reporting issues is alot easier and more pleasant. We have to remember that NT7 is beta, so problems are to be expected.
I'll stick with it, as long as their support is receptive I'll keep reporting bugs and live in hope for the day that it all runs nicely. If they can get it running well, then it's a good bit of software and NT7 does show alot of promise over 6.5 (bar the expected bugs).
The big problem for me is that NT7 still looks in many areas like it is written by an idiot - fundamental things are simply not touched, many resolving around what I see as an idiotic UI concept. They are cleaning up the internals of a bad architecture (still not multi threaded in the UI - ouch), but they need to radically change the look and feel to be something a lot easier to work with. There is a lot of stuff I simply can not really use at all - there are functions (around printing, for example) broken so brutally I wonder why they don't simply remove the stupid method to print AT ALL - like when you print executions from account performance you can not select the pages to print. Nice. I also seriously dispise having so many windows - a pain to reorganize them, and definitely missing a "minimize all / maximize all" functionality You can kill the problem here with a lot of screen space, but switching between "layouts" is not as easy as it should be. AT LEAST they finally get their act together around using a decent database Should handle many of the corruptions they did experience. But they STILL have teh stupid (and unnecessary) limit to 32 bit when using zen-fire JUST because Zen-fire is only a 32 bit api does not mean your charting system has to run 32 bit
Who would be interested in testing and providing feedback? VERY early stage (heck, I just design the connection window, after spending months on inner workings)