V12 for PRT-IG now live on Live
- This topic has 97 replies, 9 voices, and was last updated 10 months ago by
.
-
Please notice :
There is no need to sort out the memory issues. They all have been solved (but are awaiting a final test with my larger account (40+ charts / lists) which will probably happen today). However, it looks like the PRT executable(s) have been handed to IG 6 months ago, and that never received an update. Again, I just recognize all the things I created tickets for long gone, and which have been solved for PRT-IB (which is PRT itself and a different entity than PRT IG (different servers etc.).
If you want to use PRT-IG for some longer than 5 minutes when the USA stock market is open, then apply at least the button you see below. This will most probably be insufficient, so apply the bottom button. That will keep on working throughout. However, that would be for a moderately small environment (like 10 charts / lists).
So the leaking is in the data stream. Lower that and less leaks occur.
What you see in the 2nd attachment is normal memory usage. The most important is that it stays like that and not grows and grows.
The phenomena which affect it are (the loading of) indicators, the amount of candle data (thus, the more charts and lists, the more data has to be pushed through).When V12 was out a couple of months (say May 2023) it was already possible to backtest during the weekends (no data then); right from the start that already was not possible. When you’d backtest today and during the day time (markets open), I guess that not more than one run can be done before your memory will be eaten (200K bars assumed). Notice that here too I just assume an old version, so when that is refreshed by PRT all could be good instantly.
You should always have TaskManager open, ready to kill the obtrusive PRT process, because the memory usage is so harsh, that once it crosses a threshold your system will be totally unresponsive. A click with the mouse on the Java process followed by End Task, may still take a minute (you won’t see anything happen), but will work in the end. Then your system will recover.
Important : How it really turns out depends on your amount of installed memory in combination with the setting of how much one Java instance may consume. De default is 6GB, but PRT is out of control (in this V12 version for IG) and it will go beyond that. At 8GB things start to be bad.
I had that 6GB increased to 10GB for all my accounts, which is a BAD thing to do with the 32GB of internal memory I have. Obviously now each account can use 10GB, which again goes bananas and will go up to 14GB. For the PRT instance(s) this is too bad (the instance itself will stall), but with more accounts now your installed physical memory will be totally gone and all dies. And point is : you don’t see *that* coming. That’s why the TaskManager has to be ready (you won’t be able to start it when not).That’s an other question;
I am quite confident it has been solved to a certain degree (as told, I was to do the final test for the larger account, and for example, I can set back that normal Push mode already in the smaller account, but whether the large account will load in a reasonable time, I can only know when I start testing that.
Please notice I can’t test that at this moment yet, because of that “reset” thing which needs to happen (the “one time” copying of settings from V11 to V12).So that pipe line is there, but we also need to interest people over at PRT-(I think mainly IG), to implement it and for IG, re-TEST it. They may not like to do this right away again.
1 user thanked author for this post.
Thanks for the replies guys. Seems like there are issues that still need to be fixed. A definite work in progress.
But I do think that there is a valid point here – I don’t see how PRT can say they have tested v12 well. The very first thing you do when testing is open a workspace in v11 save it and then open in v12 and see if there are any issues. Which there obviously are because in v12 the workspace immediately opens with weird fonts, the chart windows are much bigger, everything is jumbled and the monitor layout is not saved ! That’s the first thing that should have been addressed and fixed before moving on ! And there is no communication from PRT to users with a note on opening the platform that “this what you need to do in v12 to fix, here are a list of known issues” etc. Pretty basic stuff really, not too much to ask.
Communication as always is key.
So I question the level, scope and validity of any further testing conducted on the above memory issues before rolling out into the live environment. And the fact that PRT are not very responsive or quick with the fixes says a lot. We just have to wait.
Today I could finally test V12 on my larger account in PRT-IB (!). The memory is fine now. This is what I sent for Technical Report text :
V12 is totally unresponsive. It just took 20 minutes to load for a 3rd time (the 2nd time I killed it because I thought it hung forever). I finally could make this Console. Here the sequence of what I did :
1. Load PRT in V12. Took 3-4 minutes. But I could not work with the PC, like now.
2. I saved to a new Template and Exit, and went back to V11.1.
3. I kicked out something else that might help, and exited V11.1 without saving.
4. I restarted V12 but killed it via TaskManager after 10 minutes or so because it did not want to load properly (all charts saying “No data for”). Lists were moving veeeery slowly.
5. I again restarted V12 and now waited longer. After 20 minutes of the same as in #4, I finally could do things, like making this Console (can hardly type in it). But see #1.Peter
Hi inv,
I am on IG (also) all right, but V12 just can’t be used by me.
OK, I thought to look at the version from 11-12, and while I indeed have that too, loading time is 5 minutes and 5 seconds (normally 45 seconds or so). There is still no Detailed Report data (2nd screenshot) – did I tell about that in this topic ? – and probably the position labels from previous trades still disappear. But I am not going to watch for that today (back to V11.1 it is).
I was told that the Detailed Report data has been fixed and waits for a next version to implement.Yes, on days like Wednesday this week my V12 in the small IB account collapsed right away too. It had been at a nice 3GB or so memory for the whole day and then when things got volatile at US open – boom at 9GB and I could barely save my system (from a necessary reboot).
Regards,
PeterPS: Just checked : loading time in the same situation under V11.1 is 60 seconds.
1 user thanked author for this post.
Find exclusive trading pro-tools on 
