Hey,
i have one tickchart (60 days, 2 volumen profiles per day, some vwaps and dayli CVD) and it loads for ever. i understand it is much to load but what i not understand is that ninja only uses 6% of my CPU at peak 11%. is it possible to make it use more and load faster or is the bottleneck somewhere else? if it is somewhere else what could it be.
and yes i know about: “close unused tabs, indicators” etc
btw i have 32 gig ram and r7 8core with 3,6ghz, i use the newest version of NT
thx in advance
If you download 60 days of tick data, that represents somewhere between 50 and 100 million ticks/bars. That’s why it takes so long. It is a download problem, not a CPU problem. I have the impression that after the take-over, Kraken reduced the number of servers. I see slower download, slower start ups, and more connection losses. On november,4 I had between 10 and 20 connection losses. That never happened before Kraken took over.
I assume that tick data is only used for intraday trading, but why you need 60 days of tick data??? I daytrade using only data from the last 12 hours, and I don’t complain about the profits.
ah ok thanks for the explanation.
maybe its bc i restart every day or bc good internet connection but i never experienced connection losses. but a friend dose also have such issues via vps.
i use 60 days bc i want the monthly and weekly vwap, maybe about 30 days would also be enough to have the recent calculated right.
I agree with marcus, 60 days for a tick chart is a LOT!!!
If you want weekly/monthly vwap, then put those on a time based chart, like 30-min. This should go much faster.
Limit your tick chart to no more than 3-5 days. Loading 60 days worth of tick chart by itself and no indicators is going to take a good amount of time. You might be able to shave off some time by doing this.
Actually loading 60 days of tick data itself is not bad. I can load it on a 500 tick chart in around 10 seconds or so. I’m assuming you are trying to load 60 days of data on a tick chart with “tick replay”. That makes a huge difference because it’s re-building each bar tick-by-tick. You’re low CPU usage is because Ninja is mostly single-threaded, meaning it’s only running on one CPU core at a time. For best performance, you want NVMe M.2 SSD and a CPU with high single core speed and obviously enough RAM. The NVM2 M.2, won’t fix the single thread issue, but it’ll give you the fastest I/O.
but how would i get the vwap then on the tickchart? i know you can use multiple data series/timeframes on one chart but can you put the 30 min monthly vwap then on the tick chart?
i got all the pc specs (maybe cpu a little old) so that shouldnt be the issue.
but could you explaine what you mean by “tick replay”? i have a tickchart with 2000 ticks and looked at the data series settings and dindt found any settings about change that.
and how much changes that the precesion of the chart?
Tick replay calculates all the bars you are loading tick by tick. You are are literally calculating every tick for the last 60 days if you have it on. Also, you can have the best specs in the world and still be have the single thread issue. I’m pretty sure all trading platforms are single-threaded because the data itself is sequential. They can run into race conditions if they try to multi-thread.
thanks for the explanation. i have it disabled as it is the normal setting. actually im loading as fast as you the tick chart itself. what seems to be the bottleneck are the indicators mainly volumen profile what takes so long to load.
My point was to have two separate charts to optimize your workspace. Time-based chart for longer term VWAP for reference (keep this on the side for viewing) and another short term chart with tick based data series (3-5 days) for execution. Just a suggestion to see if it speeds up your load time.