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 just started having a problem with Workspaces in Ninjatrader. The workspaces were taking way too long to load. I noticed that the size of the workspaces was increasing even if only a minor change was made to a single chart - say a moving average was added or even deleted and then the workspace was saved. The size of the workspace would almost double with such a small change. Over the past couple of weeks basically the same workspace has grown from about 2 KB to 14 KB. I don't know what is causing this and it is quite frustrating as a simple workspace with only a few charts will take a long time to load, or in some cases I have to shutdown, reboot and create the workspace all over again.
I have repaired the database and reset the instruments but this hasn't helped. I do not save historical chart data or record for market replay.
My computer is a Dell XPS8300 desktop with i7-2600 processor and 16GB RAM. It is used primarily for trading so I don't think it's a computer issue.
If anyone knows what is causing this or has any suggestions it would be very much appreciated.
Thanks
Can you help answer these questions from other members on NexusFi?
I have been able to make a large performance gain in NT 7 by storing the NT database files on a RAM drive and I thought that I would share what I have done.
The time taken by NT to change the time frame of a chart from 3 to 5 minutes was 46 seconds and …
Mike, thanks for the link but I'm really interested in what Ninja is doing to my workspaces and why. It just doesn't make sense that they would explode in size the way they have when there's been really minimal changes to the charts. Speeding up the load would certainly help but doesn't resolve the cause of the problem.
Sometimes workspaces get 'corrupted', and will not load, or even sometimes cause NT to not be able to start at all. Since XML files are parsed, I cannot understand how NT cannot detect an XML file with bad format or bad data. They must not be checking the file content as they read it, or they must be writing the corrupted data themselves. Also, sometimes an abnormal NT shutdown or crash will corrupt a workspace.
I generally copy a workspace XML file to a backup file as soon as I set it up, then I can restore the workspace from that backup file if I encounter any weird workspace issues.
hey Flipper,i had similar problems,and i had some corrupted data.I emailed support at nt,and they recommended some areas to start with.The first was the ninja cache,which i cleared.Also, in the ninja file,i remember having to work on some of the db andlog data.In the end ,i redid my workspace 3 times,which was annoying.
I dont know what caused thre corruption,but it might have been a bad xml file, or an indicator.Aslo,i was using momentum bars,and i switched bac to range bars.
Contact ninja support,and they are very helpful...hope this helps
I totally agree with you. It's been several years I have been waiting for a fix now and those XML corruption issues continue. I think they are simply writing out via a simple parser, meaning they are not verifying the nodes. Sometimes this causes corruptions and it will blow up NT on the way in. Not sure what to suggest - I myself am keeping backups of my workspaces but it's once again something we shouldn't have to do. Just like their data repository problems this is one of the areas where NT7 requires some refactoring. I have been waiting since 6.0 and perhaps 8.0 will get us there? ;-)
