Memory bloat just from opening NT7

[bluelou]

I'm getting memory bloat of nearly 1 GB just from opening NT7. Here's a pic from task manager. Also, I've sent my log and trace files to support. Please advise on how to stop this.

Every time I try to run a live strategy the memory blows up to >1 GB and NT shows up as "not responding". Now, even after shutting down NT7 and my PC and restarting the memory has remained bloated - and this has been for several hours.

Thx,
Lou

[NinjaTrader_Chip]

Hello bluelou,

Thank you for your post.

Please re-send your Log & Trace files and include this thread/link in your email.

Once we have an opportunity to review them & see what might be taking place here, we will be able to respond.

Thank you,

[bluelou]

Chip,
I tried resending the log & trace files but NT just hung there for 30+ min. I couldn't even use my browser. Any other ideas?

[NinjaTrader_Chip]

In this case, just isolate the individual Log & Trace files for the last day you experienced this issue.

You can find these in your (My) Documents folder in the sub-folders: (see screenshots)

1. NinjaTrader 7 > Trace > trace.2010MMDD.txt

2. NinjaTrader 7 > Log > log.2010MMDD.txt


Just attach these two text files to you email & send it to support AT ninjatrader DOT com


Once we receive them we will evaluate & try to understand what is going on.

[bluelou]

Chip,
Yesterday's log file was 342 MB and the trace file was 6 MB. How do I send this to you? Even YouSendIt.com won't allow me to send a file of this size w/o paying them $10. Do you know of another way to get this file to you?

[NinjaTrader_Kyle]

Hi bluelou,

Please compress the files in to a .zip or .rar and then upload using the free web service http://senduit.com/

[bluelou]

Kyle, I just sent the trace files since that was only 6MB.

senduit has a 100MB limit so that won't work for a 342 MB log. A few other services max out at 300MB free. I just looked at the log and I don't think it will be of that much help. It has over 1/2 milllion lines of print statements from my backtests but that's probably it.

I'll see if I can split the file in notepad++ or something like that.

[bluelou]

BTW, I've been using MSVS 2005 to debug a live strategy in NT7. During the entire process, even after terminating the MSVS debug process, NT7 shows "not responding". That means the only way for me to end the debug process in NT7 is to terminate the program in Task Manager. Is there a cleaner way to terminate debugging in NT7?

Also, I tried sending a zip version of the log file using senduit. I think I might have crashed their site during the upload b/c now the site is reporting technical difficulties.

[NinjaTrader_RyanM1]

Hello bluelou,

The size of your log file indicates there is some issue with your custom items. This is a text file meant to display debug information related to orders. If it has grown over 300 MB, then there is a lot of unnecessary logging and may explain why you're having memory issues with NinjaTrader.

Your trace file shows this line, repeated for many pages and may help you isolate what's happening here.

2010-08-02 14:37:32:954 ERROR: OBU Test

[bluelou]

Ryan,
I use the log as a place to monitor the output of my custom indicators. The log info you're seeing is mostly from StrategyAnalyzer output. The exception to this is where you see OBUTest - (OnBarUpdate test) - which is a test for live trading.

Are you saying that using the log to monitor strategy output will cause NT memory to bloat? If my indicator output should not go in the log then where do you recommend I print it to?

[NinjaTrader_RyanM1]

Hi BlueLou,

300 MB of text output per day is not typical and may cause issues loading. Using the log tab for monitoring output is fine, but something in your code or simply a large amount of tests is generating way more output than is probably useful.

If you have the need to output this much data related to your strategy analyzer tests, a better approach may be to export to an external file.

You can use the principles here:

http://www.ninjatrader.com/support/forum/showthread.php?t=3475

If the output is generated by standard tests and you have no control over where it goes, then you may need to manually monitor this file. If it gets too large transfer the contents outside of NinjaTrader's internal files.

[bluelou]

Ryan,
When you say a large log file "may" cause issues loading are you guessing that this is a problem or is this a known issue? If so, I wasn't aware that the size of the log file could affect performance.

Thx,
Lou

[NinjaTrader_RyanM1]

Hi Blue,

It's your tests that are generating such large output.

NinjaTrader reads and writes to this log file all the time. This isn't a known NinjaTrader issue - it's a tennant of computing that larger files loaded into memory will impact performance.

You're using an essentially open programming language that allows you to create tests that can potentially tax your system to the the extreme. Let us know if you feel one of your scripts is generating this output abnormally or if it's just related to the number or type of tests you're running.

[bluelou]

Ryan,
I think you've misunderstood my last comment. So, you're saying that each day's log file is held in memory for that day? For example, if I run 50 simulations and that generates 100 MB of log files (due to print statements I've put in my code) and then let's say I shut down NinjaTrader and then reopen it later the same day - are you telling me that when I reopen NT that it will also load the 100MB of log files into memory?

[NinjaTrader_JoshP]

Correct. It is not recommended you flood the log file with NinjaScript messages that are not critical. The log tab for NinjaTrader should be reserved for critical error reporting and things like that. If you are just trying to have some output, I suggest you output it to your own txt file instead of the NT logs. Please see here: http://www.ninjatrader.com/support/f...ead.php?t=3475

If you don't need these outputs for storing purposes you can even just use the Output Window and completely bypass saving these messages altogether.