|
boston
Experience: Intermediate
Platform: ninja
Trading: es
Posts: 162 since Mar 2013
Thanks Given: 31
Thanks Received: 113
|
Hi All,
I have been a user of NT since 2008 - so I am aware of all of the TIPS/tricks on cleaning the Cache, using On_Price_Change vs. each tick , deleting the TRACE folder- DB RESET and the rest.
I run what I consider NON "heavy" SINGLE workspace for only TWO INSTRUMENTS (ES+NQ). Running the Ninja RESOURC EMONITOR - seems my VOLUMETRIC charts are easily at 24,000ms.
I am only loading either 2-3 days of these charts and even tried ONLY 7 bars - and still LATENCY is INSANE - I have about 4 volumetric charts.
The only other major "heavy" chart is the 5 minuets with about simple 3-4 indicators (VWAP) and VOLUME profile which I run for 30 days lookback period.
ALSO, I have noticed that when I STRECH a CHART to beyond 2/3rds of the screen size - it FREEZES for a few seconds - and I need to wait. Happens especially with drawing simple 4-6 lines.
My laptop is a pretty strong one (though now the newest : CPU i9: 11800h , 48GB Ram, NVME storage and 3080 16gb VRAM GPU) 4k native laptop screen.
I just don't understand why running task manager and looking at the resources - NT almost always showing ONLY ranges of 11-20% CPU utilization.
I read about the idiocy of same instrument running as SAME THREAD (I know there are pro's and Cons for it) - but im seeing other products running Cumulative delta, Volume Profile, and Footprint running a few weeks of data or even months with no problem.
Sometimes PRICE at DOM vs. CHART are not synched.
Also, another phenomena I experience every now and then is when i click and TERMINATE the connection - for a FEW SECONDS the chart still moves and "animated".
Ah, one LAST thing, this happens once in a blue moon - but I place an ORDER on the DOM - and even though I placed it to go LONG BELOW where current price is - AUTOMATICALY it FILLS the moment I click the DOM - and even if PRICE is going my way and I EXIT the trade (though it was showing GREEN in the P&L on the DOm ) - it becomes a LOSS !!!. I have to RESTART to fix that - or RESET the DB - but again this is something that does not occur often.
I have to say - this is an UNACCEPTBALE performance issues that i thought originally will never occur after V.8 of ninja came out.
Would be delighted to hear other "TRICKS" or people that have experienced same thing - and inded decided to go another ROUTE to another platform.
Cheers,
S.
|