Amount of memory approaching the limit.

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

Viewing 15 posts - 31 through 45 (of 51 total)
1 2 3 4
  • 01/12/2018 at 3:48 PM #59200
    Ilaria
    Vonasi wrote:

    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.

    Hello Vonasi,

    Do you launch your platform with the launcher or in the Java mode? We suggest you use the launcher.

    If you launch it with the launcher and you have this error message even when you only have a few indicators, charts and other tools that could use a lot of RAM, please send a technical report by clicking on Help->Technical Support so that we can analyse your issue.

    Please note that we only directly receive the technical reports of IG sponsored by ProRealTime customers. If you are not in this category, please also send an email to support@prorealtime.com referring to this post and indicating the number of your IG demo account, so that we can retrieve your technical report and analyse it.

    Best wishes,

    Ilaria

    ProRealTime

    01/12/2018 at 4:08 PM #59206
    Vonasi

    Yes I use the launcher via my IG account.

    I have not been using short time frame charts for the last two days and have had no problems. I have made a minor adjustment to the way my laptop allocates RAM and will check next time I am working on short time frame charts if it has fixed the issue. I will send a report if it has not.

    Thanks for your interest.

    01/12/2018 at 4:09 PM #59207
    verdi55

    Do they already know about the decimal position size bug, or does only IG know, and they have passed it on to PRT ?

    Via support@prorealtime.com,  it may work much faster, to my experience.


    @Ilaria     : https://www.prorealcode.com/topic/cumulate-orders-and-decimal-position-size-strange-backtest-results/page/2/#post-57460

    01/12/2018 at 4:17 PM #59209
    Vonasi
    verdi55 wrote:

    Do they already know about the decimal position size bug, or does only IG know, and they have passed it on to PRT ? Via support@prorealtime.com, it may work much faster, to my experience. @ilaria : https://www.prorealcode.com/topic/cumulate-orders-and-decimal-position-size-strange-backtest-results/page/2/#post-57460

    Nicolas said he was going to make a phone call so I had hoped that may have done the trick. At the moment I feel I am doing more PRT bug fixing and problem reporting than actual development of strategies and indicators and trading.

    01/12/2018 at 4:23 PM #59211
    Nicolas
    Vonasi wrote:

    Nicolas said he was going to make a phone call

    I did, but let everyone come back from holidays first 🙂 I also know that they all been quite busy between mid December and now because of new laws about market rules, etc. (don’t know exactly what though).

    1 user thanked author for this post.
    avatar verdi55
    01/12/2018 at 4:42 PM #59220
    Vonasi

    You worked throughout your Christmas holiday so I have to assume that the rest of the IT industry did too. 🙂

    01/12/2018 at 4:48 PM #59222
    Ilaria
    verdi55 wrote:

    Do they already know about the decimal position size bug, or does only IG know, and they have passed it on to PRT ? Via support@prorealtime.com, it may work much faster, to my experience. @ilaria : https://www.prorealcode.com/topic/cumulate-orders-and-decimal-position-size-strange-backtest-results/page/2/#post-57460

    I have just forwarded the other post (on decimal position size bug) to our technical team to check whether they are already aware of it. I will add a comment under that post when I will have more information.

    Thank you for raising the issue!

    Ilaria

    PRT

     

    2 users thanked author for this post.
    avatar verdi55, avatar Nicolas
    01/12/2018 at 5:23 PM #59228
    GraHal

    Hi Ilaria, glad to see you on here

    Please forgive the daft question, just so I (and others) can be clear … what is the launcher and what is  Java mode?   Or anybody could answer please, so Ilaria can get on with important stuff.

    I / we are opening our Platforms but I’m not clear in my mind which I am using 🙂  A link to instructions will do … save you typing loads? Or even a brief 2 or 3 lines will probably suffice?

    Thank You
    GraHal

    01/12/2018 at 5:37 PM #59230
    verdi55

    Launcher mode is the normal mode, where you pre-install PRT on your computer and then start it.

    There is a link below “start your workstation” saying, if this does not work, start it in “java mode”. This used to be the old mode years ago, and it seems to be slower. You need to select how much memory you have on your computer. The pre-installed version does this and other things automatically.

    1 user thanked author for this post.
    avatar GraHal
    01/12/2018 at 5:37 PM #59231
    Vonasi

    Very soon after you posted on this forum Ilaria my PRT threw an out of memory message at me. I was testing a strategy on a 30 minute DAX chart and using the GRAPH function to graph two lines. I have sent a technical support request to PRT via the platform.

    01/12/2018 at 5:40 PM #59232
    Vonasi

    Just out of interest – I tried to launch the launcher from the .exe file the other day and it would not let me. It said that it had to be launched by logging in to IG and selecting PRT there.

    01/15/2018 at 6:24 AM #59491
    Andre Vorster

    With Win10 you need at least 16Gig RAM for good performance. If you can upgrade RAM though.

    My Computer – r/click – properties – Advanced system settings –  Advanced TAB – [Environment variables] —
    Change all your Temp file variables to C:\Temp (make a directory C:\temp first)
    In the bottom window also change these Temp paths to point to C:\Temp.

    All your temp files are now in one place and easy to find and delete all Temp files.
    Good practise is to delete all your temp files at least once a week. (I flush my Java cache and Temp files every week.)

    JAVA Update –
    I work in IT and some of our applications runs on Java and we have seen that the “latest and greatest” Java version is not always the best. Your computer software will tell you if it needs a later version of Java. Still personal preference for every user.

    Below is a basic bat file to clear all Temp and Java.
    Make a news text file. Copy and paste text below in to the txt file – save. Rename the file from .txt to .bat If you run the file it will automatically flush your Java cache and del Temp files.

    c:
    cd \
    cd c:\temp
    rmdir /s /q c:\Temp
    cd \
    cd C:\Windows\Prefetch
    rmdir /s /q C:\Windows\Prefetch
    cd \
    c:
    javaws -clearcache
    c:
    pause

    1 user thanked author for this post.
    avatar AVT
    01/15/2018 at 9:11 PM #59583
    AVT

    Thanks Andre! As a unix systemer with a Win lap I finally know how to do at least the most important deletions in a glitch like *nix!

    01/16/2018 at 3:48 PM #59658
    Nicolas

    @Vonasi

    Is the problem occurs with a specific code or with any others?

    01/16/2018 at 4:07 PM #59659
    Vonasi

    It can occur with any code and has occurred on various time frames. I do feel that using the GRAPH function is linked. I have carried on using Demo for the last two days and not had any issues. I have used the GRAPH function occasionally but have been generally trying not to.

  • Author
    Posts
Viewing 15 posts - 31 through 45 (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
prt memory leak?

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