PRT and CPU Usage

Forums › ProRealTime English forum › ProRealTime platform support › PRT and CPU Usage

Viewing 15 posts - 46 through 60 (of 61 total)
1 2 3 4 5
  • 01/14/2023 at 5:51 AM #207416
    PeterSt
    inverse wrote:

    Can someone please advise how long is the edit ‘window’ open for ….. ?

    If you mean the whole platform … 18 hours.
    Otherwise maybe elaborate on the question, please ?

    1 user thanked author for this post.
    avatar inverse
    01/14/2023 at 6:23 AM #207417
    PeterSt
    inverse wrote:

    and cores wouldn’t park / sleep

    My general advice – for a situation like yours – would be to disable hyperthreading and benefit from more cpu cycles / second. I never saw really that PRT would uses cores explicitly, so on top of all “misery” you would lose a lot of “time” on taskswitching.
    Anyway I have it off for the IMO better.

    Keep watching the memory usage. Once it is in the 8GB range, things will start to collapse and cpu usage will be excessive. But things are (memory) trashing by that time and you will notice by severe stutter on everything.

     

    1 user thanked author for this post.
    avatar inverse
    01/14/2023 at 7:36 AM #207418
    inverse

    Apologies meant Forum reply / post edit window ….

    01/14/2023 at 7:50 AM #207419
    inverse
    PeterSt wrote:

    My general advice – for a situation like yours

    No issue just making the point that odd core util in one case was related to Ryzen Chipset drivers getting hammered. I can’t say exactly how this came about and may have been a weird MS interop issue but removing and re-installing resolved the problems.

    I’m unlikely to get >8Gb in PRT use (if that’s what you’re saying) ….. I’m pretty agricultural in it’s use haha

    Thanks for the replies …. 🙂

    01/14/2023 at 9:16 AM #207422
    GraHal
    inverse wrote:

    meant Forum reply / post edit window ….

    We get 5 mins to edit our posts after first posting.

    01/14/2023 at 10:49 AM #207425
    PeterSt

    These spikes look extremely odd to me. Can you recall what you were doing there to let it spike like that ?
    Would that be Ryzen behaviour perhaps?

    Nothing within PRT inherently behaves like that (but you are going to tell me 😉 ).
    It could lead to “the” issue, once we know (hehehe).

    Edit : that first core would bee your Turbo Boost core. What in heaven’s sake would require all that contiuous “math” ?

    01/14/2023 at 10:58 AM #207427
    PeterSt

    Aren’t you using the API version of PRT ?? If that is so, it would explain a lot.

    Btw, below my cpu in the midst of a backtest, which is normal (closed markets) because all happens (PRT) server side. Not so with the API version …

    01/14/2023 at 11:12 AM #207429
    inverse
    PeterSt wrote:

    These spikes look extremely odd to me.

    Appreciate the interest and it’s as I’ve posted further up in the thread.

    It is odd that a old templates that have NOTHING or little in them loads the CPU but newly created templates won’t. Some of the templates are years old.

    I have no issue with the older templates and they can remain there till I need them, when I do I’ll rebuild them.

    It was only by chance I came across it because I wanted to pull up some historical DJIA action. All I did was open a very basic template and as a test deleted the content only to see it load CPU (details are in an earlier post).

     

    My interest here was whether those using PRT and having CPU load issues whether a simple rebuild of template could get them across the line and eliminate the issue as it did for me.

     

     

     

    01/14/2023 at 11:12 AM #207430
    inverse

    Thanks Graham.

    01/14/2023 at 11:14 AM #207431
    inverse
    PeterSt wrote:

    Aren’t you using the API version of PRT ?? If that is so, it would explain a lot.

    I’m using what’s offered by IG, it leverages JAVA underneath by the looks.

    01/14/2023 at 11:54 AM #207434
    PeterSt

    Asked differently (API) : Can you switch off your PC and your auto trading continues ?

    01/15/2023 at 12:15 AM #207450
    inverse

    Not sure is the answer, I’ve never run any systems as a set and forget strategy.

    Running PRT complete not premium.

     

     

    01/31/2023 at 2:40 PM #208865
    fj_pastor

    Hello Another one here with the problem “Out of memory” when trading on IG with several TF and screens …

    Problem started a couple of days ago. I have to restart the program every half an hour.

    Maybe it has something to do with the drawonlastbaronly instruction.

    I modified a heavy coded indicator with this feature last week. kind regards

    01/31/2023 at 3:17 PM #208867
    GraHal
    fj_pastor wrote:

    drawonlastbaronly instruction

    Assuming your last bars are 100 ish then the above usually makes everything calculate faster etc.
    If you can minimise personal indicators and also screens not being used it helps.

    How many Auto-Systems are you showing listed on the left-hand side of the Backtesting and Auto-Trading window??

    01/31/2023 at 8:42 PM #208883
    GraHal
    GraHal wrote:

    If you can minimise personal indicators

    Above is better expressed as … if you can use the minimum number of personal indicators.

  • Author
    Posts
Viewing 15 posts - 46 through 60 (of 61 total)
1 2 3 4 5

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
ig costs for prt usage
24 june 24 – cannot login to prt
6 jan 24 prt not available – too long to respond
cannot get my interactive brokers account back after cancelling prt
code to find when prt bands short term line changes colour
conversion from trading view to prt : fibonacci golden wave indicator
convert from tradingview to prt
create windows shortcut to start prt/ig
default prt vwap bands (daily) not selectable for trading system
defparam drawonlastbaronly = true in prt premium?

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