Announcement
Collapse
No announcement yet.
Partner 728x90
Collapse
NinjaTrader
Tick Replay and DB
Collapse
X
-
Tick Replay and DB
I have a few charts that require tick replay. I have noticed that after a few days, the db grew to 42,9GB !!!! At this size it starts getting unmanageable. Is there any way to set NT so the db retains only a fixed number of days of tick replay data? If not, would be a nice feature to have. Thank you.Tags: None
-
Hello,
Thanks for your post.
Do you mean that your \Documents\NinjaTrader 8\db\NinjaTrader.sdf file is that large, or your \NinjaTrader 8\db\replay folder is that large?
As of now there is not currently a way to automatically manage tick replay or database file sizes. But I could submit a request to have this included in the UI of future releases of the platform.
Please let me know if you would like me to submit that feature request.
I look forward to your reply.Josh G.NinjaTrader Customer Service
-
Hi Josh,
It turned out to be the Log folder. However, definitely yes to managing database file sizes. It would be immensely useful so please put in the feature request. Thank you.
EDIT: The size of this folder may be chocking the application. Any way to manage this?Last edited by Zeos6; 01-04-2018, 08:01 PM.
Comment
-
Hello,
Thanks for your notes.
I do not believe that the size of the log folder would be choking the application. If you are experiencing poor performance, I would like to take a look at your log and trace files to investigate the matter further. If you would like me to investigate, please write in to PlatformSupport(at)NinjaTrader(dot)com and reference this forum post.
I will submit the feature request to automatically manage the size of the db file and report back here with a tracking number as soon as it is created.Josh G.NinjaTrader Customer Service
Comment
-
Hi Josh,
I agree with you. The size of the log folder is not the issue. I know the issue now. I am using a custom indicator that requires tick replay. It has a historical null reference bug that causes massive memory leakage. The bug has apparently been reported to you guys already and hopefully will be fixed in the next release. This is a massive problem as it grinds NT to a halt so anything that can be done to fix this as quickly as possible would be most helpful and appreciated.
State = Historical. Exception: Object reference not set to an instance of an object. Stack: at NinjaTrader.Data.BarsSeries.GetTime(Int32 index) at NinjaTrader.Data.BarsSeries.GetSessionEndTime(Int3 2 index) at NinjaTrader.Data.Bars.GetSessionEndTime(Int32 index) at NinjaTrader.NinjaScript.TimeSeries.get_Item(Int32 barsAgo) at MyIndicator.NT8.CoreIndicator.BarUpdate() at MyIndicator.NT8.TickIndicator.BarUpdate() at MyIndicator.NT8.myIndicator1.BarUpdate() at MyIndicator.NT8.CoreIndicator.OnBarUpdateException Wrapper()
Comment
Latest Posts
Collapse
Topics | Statistics | Last Post | ||
---|---|---|---|---|
Started by Pattontje, Yesterday, 02:10 PM
|
2 responses
14 views
0 likes
|
Last Post
by Pattontje
Yesterday, 11:49 PM
|
||
Started by flybuzz, 04-21-2024, 04:07 PM
|
17 responses
229 views
0 likes
|
Last Post
by TradingLoss
Yesterday, 11:45 PM
|
||
Started by agclub, 04-21-2024, 08:57 PM
|
3 responses
17 views
0 likes
|
Last Post
by TradingLoss
Yesterday, 11:42 PM
|
||
Started by TradingLoss, 04-21-2024, 04:32 PM
|
4 responses
43 views
2 likes
|
Last Post
by TradingLoss
Yesterday, 11:40 PM
|
||
Started by cre8able, 04-17-2024, 04:16 PM
|
6 responses
56 views
0 likes
|
Last Post
by cre8able
Yesterday, 09:20 PM
|
Comment