Amount of memory approaching the limit.

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

Viewing 15 posts - 16 through 30 (of 51 total)
1 2 3 4
  • 01/11/2018 at 9:15 AM #58957
    GraHal

    Just another thought … Check Help/TecnicalReport/Other and see if the RAM monitor reads same RAM value as your Advanced System Care monitor.

    it will be easier for other users to help / replicate our investigation using Help/TechnicalReport/Other.

    01/11/2018 at 12:50 PM #59034
    Vonasi

    Good point GraHal and interesting result. They are different. PRT thinks it is using less RAM than Task Manager says it is. Performance Monitor agrees with Task Manager (well to a roughly rounded result anyway). Image attached but unable to get PM on same screen as TM and PRT for some strange reason so it is not shown.

    I have not been using the GRAPH function this morning and have had no annoying messages.

    01/11/2018 at 12:57 PM #59037
    verdi55

    Task manager always reports more memory for java than the PRT error section.

    If your problem persists, and you have a PRT premium account, try to contact support. They helped me once on a similar issue and worked with me interactively over 2 days until the memory problem was solved.

    01/11/2018 at 1:06 PM #59039
    Vonasi

    I just edited my last post (so you may have missed it) to say that I have not used GRAPH today and have had no issues. Unfortunately I am not Premium but IG complete account.

    01/11/2018 at 1:11 PM #59040
    verdi55

    Dumb question : how do I edit a post here ?

    01/11/2018 at 1:28 PM #59045
    Vonasi

    You have five minutes to edit it after posting after that the edit option disappears from the Edit, Reply, Thank, Quote, Report options in the top right of you post.

    Sometimes a delete option would be nice too.

    01/11/2018 at 1:30 PM #59046
    verdi55
    Vonasi wrote:

    I just edited my last post (so you may have missed it) to say that I have not used GRAPH today and have had no issues. Unfortunately I am not Premium but IG complete account.

    On a PRT premium account, you can run 10 backtest parameter optimizations in parallel, on IG complete it used to be only 1. Saves a lot of time.

    01/11/2018 at 1:36 PM #59049
    Vonasi
    verdi55 wrote:

    On a PRT premium account, you can run 10 backtest parameter optimizations in parallel, on IG complete it used to be only 1. Saves a lot of time.

    Yes I think that IG complete just queues them up and does one after the other. My brain struggles to remember what I was trying to prove with just one let alone ten. It is a bit like my RAM so I’m not sure that could handle 10 optimizations at the same time either – especially if they all have a GRAPH function in them. It can’t handle one at the moment!

    01/11/2018 at 10:31 PM #59113
    Vonasi

    So today I was working away all day on a 30 minute chart and making a conscious effort to not use the GRAPH function. No issues at all – no annoying message. So tonight I started using GRAPH with three lines and….. no problems so far. RAM usage at 1.85GB and not rising. Go figure?

    01/11/2018 at 11:08 PM #59116
    verdi55

    In my experience, graph commands may sometimes cause memory problems or they may not. For example, I’m running several versions of the pathfinder backtest now with a lot of graph commands, just out of interest, and there are no memory problems at all. On the other hand, in most cases when I did have memory problems, graph commands were involved. So my conclusion is : when there are memory problems, the first step is to leave graph commands away. The problems may depend on the total PRT configuration : how many charts, how many indicators, how many bars, how many graph commands, etc.

    01/11/2018 at 11:11 PM #59118
    verdi55

    Oh, and I remember that graph commands in a 10 second chart caused huge memory problems rather quickly. So, maybe it is an issue of data accumulation over time.

    01/11/2018 at 11:14 PM #59120
    Vonasi

    Yesterday I reduced everything down to absolute minimum. No indicators, just one chart, no other windows at all and all day I had the annoying message I could not backtest a damned thing. At the moment I have indicators galore, lots of others windows and three lines on a graph and not a single problem with RAM. It is sitting happily at just(!) 1.8GB. It is all very random if you ask me.

    01/11/2018 at 11:16 PM #59121
    Vonasi
    verdi55 wrote:

    Oh, and I remember that graph commands in a 10 second chart caused huge memory problems rather quickly. So, maybe it is an issue of data accumulation over time.

    Well I was on a minute chart all day yesterday and today I am on a 30 minute chart. Seems to me then that PRT need to look into the GRAPH function on very short time frame charts eating up RAM and never giving it back.

    01/12/2018 at 8:35 AM #59136
    Andre Vorster

    I did not read all the comments but … May be I can help.

    1. Which operating system are you using? How much RAM?
    2. Which Java version? (open command prompt – type in “java -version” OR – ControlPanel – Java – “about”)

    Check the following –
    3. My Computer – r/click – properties – Advanced TAB – [Environment variables] – –Where does your Temp point to? It will point to some directory.
    4. My Computer – r/click – properties – Advanced TAB – [Settings] – Advanced TAB – [Performance Settings] – Advanced TAB – [Change] – –What is the settings for your page file.
    5. My Computer – r/click – properties – Advanced TAB – [Settings] – Advanced TAB – [Performance Settings] –  –Set visual effects to “best performance” (this optional because it will remove all the fancy visual effects but increases performance)

    I have not had any problems with FireFox – Use FireFox 64 bit version.

    My system settings are as follows:
    1. Windows 10 64bit – 32Gig RAM.  (you wont have good performance below 16Gig RAM)
    2. Java version – Ver.8 update 91 (JRE version – not JDK version)   ### DONT AUTO UPDATE JAVA ###
    3. Temp files point to C:\Temp (user variables and system variables)
    4. No paging file set.  (this depends on RAM – less than 16Gig ram set it to System managed)
    5. Best performance (this takes away all the fancy bells&whisteles that just east memory)

    1 user thanked author for this post.
    avatar GraHal
    01/12/2018 at 12:26 PM #59172
    Vonasi

    1. Windows 10 8GB RAM.

    2. Java Version 8 Update 151 (build 1.8.0_151-b12)

    3. C:Users\………..\App\LocalData\Temp

    4: Page file was set to a custom size. I have changed this to system managed now. No paging file set.

    5: Was set to let Windows choose what’s best. have now set to best performance.

    Can I ask why you suggest not auto updating Java?

    I will restart laptop and see if the changes make any difference. Thanks for your assistance.

     

  • Author
    Posts
Viewing 15 posts - 16 through 30 (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