PRT clearing temporary files when backtesting

• 12/13/2020 at 1:10 PM #153567
  Franro

  After optimizing a system in approx 20 hours and it has gone 20% loading. I got this message “Warning: in order to clear temporary files, your connection will expire soon. You should save your modifications now and restart application. Attached a file.

  So I guess this have been happening several time while night when im trying to optimize. Everytime i wake up in the morning the program is shut off. I lost several hours of work and I did manage to catch the message this time.

  Even though i pressed exit later same message came with 0 minutes then it automatically closed. [MODERATION: DELETED BAD WORDS ; RESPECT THE POSTING RULES]

  

  Franro

  Participant

  Topics: 23

  Replies: 214

  Been thanked: 23 times
  12/13/2020 at 1:17 PM #153569
  Franro

  I was launching my prt using java mode through ig (as that is the best (fastest) way to optimize algos?) as you can choose > 8 GB ram.

  Correct me if im wrong..

  

  Franro

  Participant

  Topics: 23

  Replies: 214

  Been thanked: 23 times
  12/13/2020 at 3:26 PM #153582
  robertogozzi

  PRT is shut down every 18 hours (it was 12 up to a couple years ago) to clear some temp files.

  You need to make your backtests shorter and I suggest that YOU shut it down before it does that itself.

  I shut down, and immediately launch it again, twice a day, at around 09:00 and around 20:00, to make sure it’s within 18 hours.

   

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 16581

  Been thanked: 3704 times
  12/13/2020 at 3:31 PM #153583
  Franro

  Why would it be like that its 2020..

   

  Well its hard when you have a long code and when 6000 combinations takes 1% per hour to load… So there is no other way around it?

  

  Franro

  Participant

  Topics: 23

  Replies: 214

  Been thanked: 23 times
  12/13/2020 at 4:09 PM #153585
  GraHal

  Franro wrote:

  So there is no other way around it?

  Optimise with coarse / wide steps first then refine in to narrower steps after each optimiser run.

  20 hours to optimise … I get impatient after a few minutes so I use the above method.

  Or alternatively optimise 1 variable at a time or at most 2 at a time.

  1 user thanked author for this post.

  robertogozzi

  

  GraHal

  Participant

  Topics: 205

  Replies: 8534

  Been thanked: 2094 times
  12/13/2020 at 4:17 PM #153586
  robertogozzi

  Use this box https://www.prorealtime.com/it/contatto to tell what you don’t like, what you like and what you suggest.

   

  1 user thanked author for this post.

  Franro

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 16581

  Been thanked: 3704 times
  12/13/2020 at 4:27 PM #153588
  Franro

  I use wide steps and trying to include about 6 variables.. It is a long code which takes time therefor it would be nice if the program  didnt shut off every 18 hours atleast that you can have the option to not do it.

  

  Franro

  Participant

  Topics: 23

  Replies: 214

  Been thanked: 23 times
  12/14/2020 at 12:13 AM #153614
  XORANDNOT

  I think one reason it shuts down every 18 hours is to get people to think more carefully about how to optimize their codes without having to use 100,000 combinations. Most of the time, there are easier and faster ways. You will end up with a curve fit either way.

   

  Normally, it is more important not to find “the best” of 6.000 combinations, but rather to see whether you get broad ranges of all variables where they work reasonably well. With only 100 out of 6000 combinations showing up in the end, you won’t see this.

  1 user thanked author for this post.

  Nicolas

  

  XORANDNOT

  Participant

  Topics: 12

  Replies: 179

  Been thanked: 39 times
  12/14/2020 at 10:29 AM #153651
  Nicolas

  Backtests are made server side, they can take longer if you are not alone in the queue. Try to reduce your combinations like it has been suggested.

  I removed the bad words form your post, please be polite in your next posts.

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20838

  Been thanked: 4749 times
  12/26/2020 at 5:33 PM #155257
  Berra

  How much are the backtest time depending on the computer performance or net speed capacity?

  

  Berra

  Participant

  Topics: 1

  Replies: 6

  Been thanked: 0 times
  12/26/2020 at 7:08 PM #155265
  GraHal

  Berra wrote:

  How much are the backtest time depending on the computer performance or net speed capacity?

  Very little dependecy whatsoever

  In my opinion … 4GB RAM and above helps prevent hanging / freezing.

  PRT Servers do all the processing so user computers do not need to be latest models etc.

  

  GraHal

  Participant

  Topics: 205

  Replies: 8534

  Been thanked: 2094 times
  12/26/2020 at 8:11 PM #155269
  Monochrome

  It dosent seem to process the calculation of indicators on the servers.  Each indicator takes up a cpu core.

  So if you use lots of indicators i would recommend lots of cores and ram.

  

  Monochrome

  Participant

  Topics: 16

  Replies: 109

  Been thanked: 44 times
  12/26/2020 at 9:10 PM #155272
  GraHal

  Monochrome wrote:

  Each indicator takes up a cpu core.

  You talking about Indicators displayed on charts (not Indicators used in backtests)?

  

  GraHal

  Participant

  Topics: 205

  Replies: 8534

  Been thanked: 2094 times
  12/26/2020 at 9:51 PM #155277
  Monochrome

  Yes indicators displayed on charts.

  I have a slow cpu and on 200k it takes quite some time to load.

  1 user thanked author for this post.

  GraHal

  

  Monochrome

  Participant

  Topics: 16

  Replies: 109

  Been thanked: 44 times
• Author
  Posts