V12 for PRT-IG now live on Live
-
What ver of v12 are you running Gra?
PRT Complete v12 … see attached
Seems you’re ahead ….
I’ve reinstalled again, it’s my life’s work now 🙂
And we’re on the same rev. as you now, kiss of death here mate!
Help center reports the same as before but “about” marries with what you saw.
Version : v12.0.20240111030019
inverse, All – to be sure we keep on talking about the same subjects in this thread : as far as I am concerned the memory issues have been solved.
(of course I am ahead too – haha)But I have been tracking this continuously, and the 2x V12 (one IG, one IB) which is contained in the below little list, even consume LESS memory now.
I assume it is still so that more memory comes handy when Backtesting (I have 10GB assigned), but it seems that things don’t choke any more.
For the V12 on IB I still use Standard data stream (I just don’t need the Push or better) and for the V12 on IG I use the Push Comfort (middle option). No issues with that too.The loading of a somewhat larger setting (my IG) during day time over here (say 1pm) is quite undoable (could take up to 5 minutes).
Putting through an order (from ProOrder Not Running to Running) is virtually impossible (takes 2 minutes). This is with both V12 on IB and IG. ProOrder could still be the cause of a large portion of slow loading, although the Detailed Reports are certainly to blame for the slow loading as well.New to this thread is :
I think it was Sat two weeks back that something seemed to be amiss on the PRT server(s) and that Backtesting went slower than normal (or maybe I used an Instrument with more ticks – can’t tell really). There it became apparent that Backtesting was undoable on V12, but doable on V11. This was both IB.In all events mentioned above, it feels like PRT is now using too FEW memory. Let’s say that these are my senses and I can’t really prove that. But obviously, if a program is given too few memory, things may start to thrash (like in disk thrashing – now re-using of array elements, for example). I told the people in Paris about this, say 6 weeks ago, but then it was only something I “saw” (like you see the 750K below – this just doesn’t seem right). But, when I now practically see what happens with putting through an order (or Stop one for that matter), … how can that take minutes. It is so sooo wrong (compared to V11 where this takes 5-10 seconds). And Yes, all happens on the very same PC.
Do I currently have more to nag about ?
Well, the Order Labels seem to be fine now (I think since GraHal’s latest version which is also my version), but with my eye on the IG V12 which applies trailing I see Trailing Labels disappear, while my code really does not stop trailing once it starts with that. Internally the trailing is fine (I suppose this is to be translated as : the Pending Stop orders I place, are still dealt with fine, (thus this is not real PRT trailing as such)).I will hand this post to PRT, so they at least will know how *I* look at things currently. If you guys deem it necessary to add things, just please do so.
How can we put through an Order (to execute a trade?) from a Not Running System?
More coffee GraHal. More coffee. 🙂
But undoubtedly my English plays a role here too.
Anyway easy enough : Move the Systems from the bottom part to the middle part (via the green button – not visible here).
(for PRT IB users – The top part is not there in V12, dunno why)Treating one order takes around 2 minutes during day time (in the weekend 1 minute). This does not relate to the number of Not Running systems (as far as I can notice).
Hahahaha, 4976 eh ?
Well, or your counting (PRT’s) is a little off and nothing will be added any more, or you have 24 trades to go (maybe 1 extra).
Meaning :I now see that they fi-nal-ly did something about this. It has turned into 5000 max (5001 for the 1 extra). In other words : whether I show Nasdaq only or everything, with me it shows 5001.
Could that matter between you and me ? maybe. At least I can see that building the report takes 30-45 seconds which in your case could be about half of that. That still does not justify the 2 minutes wait for making a System live (from Not Running to Running).May I ask, your figure is also about Live ? (not Demo).
Later … Maybe there is more beyond the horizon …
The second little screenshot is from my main account. This was limited at 10000 (special setting for me). I ran out of that 10000 limit 3-4 years ago. BUT it showED half trades. So now it shows 8075 trades, which should be (??) full trades (In + Out = 1 trade) because the closed trades nicely starts at the time I started with PRT (the IG report starts at Sep 2022 which definitely is not when I started with PRT). So … maybe the limit is still there, but now is about 10000 full trades. Man, you have no idea how often I complained about this – and now they done it ? And to avoid confusion, I never asked for expanding the limit for my IG account. So that always was stuck at 3000 (1500 full trades).
Do notice, however, that this is about IB and V11 (I can’t start V12 with this account (takes too long) but I can try tomorrow (Saturday)). Btw, building this report takes something like 10 seconds. Thus, it comprises (for result) say two times more and is at least 3 times faster – that’s net 6 times faster. But careful, this is IB, while the other with V12 is IG. Maybe that matters.PRT PRT PRT, where is your change log (Release Notes). We can be happy about many things. But if we don’t know about them … Like in this case; I limited all my reports to a more recent date for some reference as I did not even know this had changed (improved !!).
For V12 this does not help much yet, as it can’t be part of the start-up procedure (takes too long and all will hang on it). But I can fire up that later after startup.
- You must be logged in to reply to this topic.
Summary
This topic contains 97 replies,
has 9 voices, and was last updated by 
2 years ago.
Topic Details
| Forum: | Platform Support: Charts, Data & Broker Setup |
| Language: | English |
| Started: | 11/30/2023 |
| Status: | Active |
| Attachments: | 35 files |
