Amount of memory approaching the limit.

Forums › ProRealTime English forum › ProRealTime platform support › Amount of memory approaching the limit.

Viewing 15 posts - 1 through 15 (of 51 total)
1 2 3 4
  • 01/10/2018 at 3:47 PM #58864
    Vonasi

    Today PRT demo has decided to throw at me this message every few seconds.

    Screenshot_3-1

    I have one chart with one indicator open, one strategy that I am testing and one window showing me how my running live strategies are performing so not exactly excessive usage! Java is stuck at 4.0GB RAM usage.

    01/10/2018 at 5:18 PM #58887
    GraHal

    Just an idea, but did you clear your java cache out at any point recently? It might help  or at least be useful to know if it makes and difference or not?

    I used to get that message loads ages ago, but I can’t recall any definite thing I did to stop getting it, sorry.

    Aha I remembered … I stopped using Firefox!

    What browser do you use Vonassi?

     

    01/10/2018 at 5:41 PM #58890
    GraHal

    I noted that Firefox tends to eat RAM (ram used creeps up and up even without opening more tabs etc) especially after it has been open for a few hours (well documented on the net).

    I use Chrome now.

    01/10/2018 at 6:03 PM #58893
    Vonasi

    I shut down PRT Demo. Cleared the Java cache. Restarted PRT Demo and now once again Java is up to 4.0GB RAM and I am getting the messages again. It makes testing impossible.

    I use Opera (Don’t ask why – I have just used it for so long now that I can’t bear to change!) I have only two tabs open and Opera is using 350Mb RAM.

    01/10/2018 at 8:31 PM #58916
    Vonasi

    Happened again so I closed PRT, rebooted, reinstalled PRT started it again and within 20 minutes RAM up to 4GB and that damned message popping up all over the place.

    I’m working on a 1 minute chart – not sure if that is relevant but I will move onto a different project on a different time frame just to see.

    01/10/2018 at 8:49 PM #58918
    Vonasi

    I think I found the previous discussion on this at https://www.prorealcode.com/topic/out-of-memory/ and the solution appeared to be buy a faster computer! I find it hard to believe that 8GB is not sufficient to run one small backtest on 100k bars on a minute chart without running out of memory. PRT’s memory usage is appalling if this is the case.

    01/10/2018 at 9:10 PM #58921
    Vonasi

    So I shut down the strategy, got rid of every indicator, moved to a four hour chart, got rid of every other window (the only other one!) and still PRT gives me this damned message and is using over4.5GB of memory. Does PRT never let go of memory once it has got hold of it!?

    01/10/2018 at 9:36 PM #58923
    Vonasi

    So the saga continues but maybe with some slight idea how to avoid that damned message. I shut down down PRT yet again. Reloaded it in a four hour chart and ran a different strategy backtest. All was OK and RAM usage only about 1GB. So I loaded up the original strategy and started backtesting that at the same time – no problem and only about 2GB of memory being used. So basically PRT cannot cope with running a backtest on a simple strategy on a 1 minute chart without taking the RAM usage up to 4.5GB and getting stuck there until you shut PRT down again.

    This is a major limitation and a major RAM usage issue that needs fixing.

    From watching the RAM usage it does appear that PRT’s RAM usage creeps up and up and it rarely ever releases any RAM.

    01/10/2018 at 10:17 PM #58928
    GraHal

    I backtest 100,000k bars on a 1 minute TF with no issue.  I am running 8GB RAM also.

    Your statement confused me …  So I loaded up the original strategy and started backtesting that at the same time – no problem and only about 2GB of memory being used. 

    The original Strategy being the 1 minute Strat??

    More Thoughts

    How long is it since you reinstalled windows on your PC / laptop?

    When I had same issue over and over (as you currently) my PC was grindingly slow to boot up etc and could only run very few Apps etc at same time. Anyway I did a 100% fresh install  of windows and have not had the memory messages since?

    The PC I had the issues on had windows 10 installed as an ‘upgrade over windows 7’.  Any of this sound familiar to your OS??

    GraHal

    01/10/2018 at 10:29 PM #58929
    Vonasi

    Yes the original 1 minute strategy on a 4hr hour time frame just to eliminate it as a problem with that strategy.

    I have never done a clean install of Windows10. This one is over Windows 8 if I remember right. I have no other issues. Everything else works just fine and fast it is just PRT that grinds to a halt. I had some issues a few weeks back after an update but Windows10 is actually pretty efficient at repairing itself so all is fine now. I noticed that with just one strategy  backtesting on a 4hr chart that  PRT went up to almost 3GB usage. I have now not touched PRT for half an hour and it has gone back down to 1.75GB  so it does release RAM sometimes. It seems crazy that PRT requires so much RAM. I have 8GB of which almost 7GB is usable and PRT wants 4.5GB to run very little and then complains that it is not enough!

    01/10/2018 at 10:51 PM #58933
    GraHal

    Ah gotcha re the ‘original’ Strat.

    Where are you reading the RAM using Help / Technical Report on the PRT Platform?

    Next time I backtest I’ll check what my RAM reading is. Anyone reading this could also do the same  please so we can bottom this out for Vonasi.  You must feel like topping yuorself!? 🙂

    There may be some tie in with the upgrade from Windows 8  (as mine was upgrade was W7).  

    https://www.drivethelife.com/windows-10/fix-high-ram-cpu-memory-usage-after-windows-10-update.html

     

    01/10/2018 at 11:02 PM #58934
    verdi55

    “graph” commands consume a lot of memory, and never release it back again, even when you close a backtest

    01/10/2018 at 11:09 PM #58937
    Vonasi
    verdi55 wrote:

    “graph” commands consume a lot of memory, and never release it back again, even when you close a backtest

    Very interesting. I was graphing three lines in the backtest. It is pretty hopeless if you can’t put a graph in because it uses too much RAM! Definitely something that PRT need to improve I think.

    01/11/2018 at 12:14 AM #58944
    Vonasi

    GraHal I am reading the memory usage Advanced System Care’s performance monitor that monitors RAM CPU DISK and temperatures (lost a laptop once to fluff in the cooling vents!) I also check in the task manager.

    Verdi55 may be onto something with the graph suggestion. I had three lines on a graph and I have removed that and have not had the message for a while. Saying that as I write this I am up over 4GB RAM and there is the message……. doh!

    01/11/2018 at 12:49 AM #58949
    Vonasi

    So PRT was stuck at over 4GB again so I shut it down and started it again and have now been running for a while backtesting with no problems with no graph instructions. RAM usage crept up to 1.29GB and is still creeping. I think the graphs are a major issue but PRT is just generally very RAM inefficient it seems. Still creeping up as a backtest continues. Will see what happens when it finished – will the RAM ever drop!

  • Author
    Posts
Viewing 15 posts - 1 through 15 (of 51 total)
1 2 3 4

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
backtesting does not work which a great amount of time units

Create your free account now and post your request to benefit from the help of the community
Register or Login