PRT crashes during export

• 07/24/2021 at 3:51 PM #174090
  GraHal

  I agree 110% re a central repository for Algos.

  If only PRT would / could work on improvements that will make users life easier / more efficient when we carry out everyday repeated tasks then we would all be happier bunnies!

  The many bells and whistles provided on version 11 should have been secondary to providing for a more enjoyable reliable everyday experience using the PRT Platform.

  1 user thanked author for this post.

  PeterSt

  

  GraHal

  Participant

  Topics: 204

  Replies: 8440

  Been thanked: 2049 times
  07/25/2021 at 10:02 AM #174110
  PeterSt

  GraHal wrote:

  Also you may wish to try Malware Hunter free version and then you will also get that little utility that I show on the screen shot I posted above

  Hi GraHal – I don’t see any screenshot you are referring to. Also, as far as I can see we’d need to install what you see in the first attachment, and not the main Mailware program you referred to. OR … or I can not find the button to launch the RAM cleaner utility you refer to. The latter with the notice that I see an .exe and .dll’s in the installed folder that look to be related to RAM cleaning. Anyway, this is what I found :

  1. See first attachment. Install that. Run it.
  2. See second attachment. Choose Optimize & Improve from the left pane. From there click the Memory Optimizer link you see under the mouse arrow.

  GraHal, if this is not what you are using, please let us know.
  I am going to try this myself, and hope that the ever filling memory (because of memory-leaking PRT) can be freed so the eventual crashes will stay away.

  Thank you for pointing out this utility !

  

  PeterSt

  Participant

  Topics: 72

  Replies: 2333

  Been thanked: 701 times
  07/25/2021 at 3:21 PM #174125
  GraHal

  Have you got a wiper like attached at the red arrowhead?

  It’s bit weird as I lost the wiper thingy once ( 🙂 ) and couldn’t for the life of me see how to get it back but it popped up again at next PC boot up!

  

  GraHal

  Participant

  Topics: 204

  Replies: 8440

  Been thanked: 2049 times
  07/25/2021 at 4:10 PM #174128
  PeterSt

  I read your message, let it be for a while because I did not know where to look for it, and suddenly I see it in the top-right of my screen.

  What I pointed out (previous post) did not do a thing to PRT’s memory. But this is !!

  Side note : coincidentally something crashed when I was making the screenshot (see 2nd attachment). Maybe it is not important.

  What that “wiper” seems to do, is throw out about all memory from PRT (16 or so MB remained from 2GB), which herself next slowly reads it back from the paging file. So I now slowly see it increase again (while PRT is idle as far as I’m concerned – no backtesting and no live trading feeds as well).

  I have yet to see how it works out – will report back when I see something useful.

  

  PeterSt

  Participant

  Topics: 72

  Replies: 2333

  Been thanked: 701 times
  07/25/2021 at 4:16 PM #174132
  PeterSt

  Maybe superfluously :

  It is not that PRT eats all the memory I have available. For example, when I started earlier today it had 1.5GB or so in use (my system contains 32GB) and an hour ago it had grown to over GB. This is where I restarted PRT in order not to run into trouble (which will happen when it is into the 6GB’s).

  For now it stopped loading back from the page file (well, I assume it was doing that) and it fixated at 956M while a 1M bars backtest is running.

  It all looks quite odd. If it only helps … (fingers crossed).

   

  

  PeterSt

  Participant

  Topics: 72

  Replies: 2333

  Been thanked: 701 times
  07/25/2021 at 5:41 PM #174136
  GraHal

  I can’t decide (from what you have written) if the RAM release wiper is helping your PRT performance or not?

  It helps mine, but then I have only 8GB RAM on my PC.

  

  GraHal

  Participant

  Topics: 204

  Replies: 8440

  Been thanked: 2049 times
  07/25/2021 at 7:15 PM #174140
  PeterSt

  I know know it does NOT help.

  Since my last post I used the Wiper 3 or 4 times, and indeed initially it throws out all of the memory from PRT’s instance. But the longer you’re in, the faster it is loading back everything.
  10 minutes ago I could see it going wrong (PRT suddenly used 8GB) and after Wiping the memory fairly quickly PRT consumed close to 8 GB again. Then the dreaded message appeared (“The last activity required more memory” or thereabouts). So I quickly used the Wiper again, but within 10 seconds it was at over 9GB and everything went without response. In between these jobs I exported my program, so all is fine regarding that.

   

  GraHal wrote:

  It helps mine, but then I have only 8GB RAM on my PC.

  Yeah – because PRT starts to use more and more memory, it surely will help if memory from other (dormant) programs is moved out of the way.
  So in your case your total amount of memory is the bottleneck first. PRT starts using e.g. 6GB and your system will choke; When you’d have more memory (my case), the system is fine, but PRT chokes.

  I know by know that the size of the program is crucial. Maybe you recall my elaboration about typing in the editor letting increase the memory more and more until all chokes ? well, today the program is over 4K lines and it is very unresponsive right from the start. PRT is just not made for this. Editing during the weekend is still OK with this, but when live backtesting (throughout the week) is commencing, it is almost undoable.
  It leaves me removing the program comments. Haha.

  

  PeterSt

  Participant

  Topics: 72

  Replies: 2333

  Been thanked: 701 times
  07/25/2021 at 7:49 PM #174142
  GraHal

  PeterSt wrote:

  In between these jobs I exported my program, so all is fine regarding that.

  Above is what I was advocating … a way to release RAM in order to Export and / or Quit and Save (as opposed to frozen / hanging and Task Manager Exit All).

  PeterSt wrote:

  PRT starts using e.g. 6GB and your system will choke;

  My PRT Ram never goes much above 2.5GB, maybe 2.6GB ish as I think there is a inbuilt setting that PRT RAM will never be more then x % of the total available.

  You may do well to somehow tell your PRT Platform  that your RAM is 8GB then you also would be limited to 2.5GB ish (total used / hogged by PRT)  and as you have total of 32GB you may have no problems??

   

  

  GraHal

  Participant

  Topics: 204

  Replies: 8440

  Been thanked: 2049 times
• Author
  Posts