Discussion of article "LifeHack for traders: Fast food made of indicators" - page 10

 
Anatoli Kazharski:

Then this result:

//---

You have the first result on hot, the second on cold. Are you sure it's an HDD and not an SSD? 350 gigabyte broom? And too time coincides with my SSD (and the rest of the hardware is exactly the same).

2018.01.26 15:49:12.924    Terminal    Windows 10 (build 16299) x64, IE 11, UAC, Intel Core i7-4770  @ 3.40GHz, Memory: 24633 / 32655 Mb, Disk: 51 / 222 Gb, GMT+3

2018.01.26 15:50:05.361    Core 1    EURUSD,M1: 9444372 ticks, 146040 bars generated. Test passed in 0:00:07.156 (including ticks preprocessing 0:00:01.250).

I'll try it on the broom.

I made a symlink on HDD to the tester folder, nothing dramatically changed. Either the bottleneck is not in the tester folder, or the problem is not in the broom. tkc files are now on HDD

2018.01.26 16:25:22.984    Core 1    EURUSD,M1: 9444372 ticks, 146040 bars generated. Test passed in 0:00:07.265 (including ticks preprocessing 0:00:01.265).


 
Комбинатор:

You got the first result on hot, the second on cold. Are you sure it's an HDD and not an SSD? 350 gigabyte broom? And too time coincides with my SSD (and the rest of the hardware is exactly the same)

HDD is 500GB (logical drive C at ~150, D at ~350).

I try again with the same parameters, restarting the terminal:

2018.01.26 15:25:29.922 Terminal        MetaTrader 5 x64 build 1755 started (MetaQuotes Software Corp.)
2018.01.26 15:25:29.941 Terminal        Windows 10 (build 16299) x64, IE 11, UAC, Intel Core i7-4770  @ 3.40 GHz, Memory: 3822 / 8075 Mb, Disk: 35 / 319 Gb, GMT+3

//---

2018.01.26 15:39:30.657 Core 1  authorized (agent build 1755)
2018.01.26 15:39:30.659 Tester  EURUSD,M1 (MetaQuotes-Demo): testing of Experts\Examples\MACD\MACD Sample.ex5 from 2017.09.01 00:00 to 2018.01.26 00:00
...
2018.01.26 15:39:36.843 Core 1  EURUSD,M1 (MetaQuotes-Demo): generating based on real ticks
2018.01.26 15:39:36.843 Core 1  EURUSD,M1: testing of Experts\Examples\MACD\MACD Sample.ex5 from 2017.09.01 00:00 to 2018.01.26 00:00 started with inputs:
2018.01.26 15:39:36.843 Core 1    InpLots=0.1
2018.01.26 15:39:36.843 Core 1    InpTakeProfit=50
2018.01.26 15:39:36.843 Core 1    InpTrailingStop=30
2018.01.26 15:39:36.843 Core 1    InpMACDOpenLevel=3
2018.01.26 15:39:36.843 Core 1    InpMACDCloseLevel=2
2018.01.26 15:39:36.843 Core 1    InpMATrendPeriod=26

First test (on cold):

2018.01.26 17:11:34.824 Core 1  final balance 10168.90 USD
2018.01.26 17:11:34.824 Core 1  EURUSD,M1: 9753093 ticks, 147480 bars generated. Environment synchronized in 0:00:00.094. Test passed in 0:00:08.078 (including ticks preprocessing 0:00:01.234).
2018.01.26 17:11:34.824 Core 1  EURUSD,M1: total time from login to stop testing 0:00:08.172 (including 0:00:00.094 for history data synchronization)
2018.01.26 17:11:34.824 Core 1  607 Mb memory used including 44 Mb of history data, 256 Mb of tick data

//---

Second test (hot):

2018.01.26 17:12:35.048 Core 1  final balance 10168.90 USD
2018.01.26 17:12:35.048 Core 1  EURUSD,M1: 9753093 ticks, 147480 bars generated. Test passed in 0:00:05.985.
2018.01.26 17:12:35.048 Core 1  597 Mb memory used including 44 Mb of history data, 256 Mb of tick data
 
Anatoli Kazharski:

So we have to find another bottleneck. Or another way.

 
Комбинатор:

So we need to look for another bottleneck. Or another way.


Turn on your Bitlocker

 
Rashid Umarov:

Turn on your Bitlocker.

Nah, I'm not willing to make that kind of sacrifice.

 
Rashid Umarov:

Made the MACD SaMple from the delivery on your settings. And where does EURO in the balance come from, isn't that the point?

And the testing time is still much longer than yours.

Result on my home computer. Testing time - 10 seconds. HDD

2018.01.27 05:00:10.164 Core 1  agent process started
2018.01.27 05:00:10.756 Core 1  connecting to 127.0.0.1:3000
2018.01.27 05:00:10.756 Core 1  connected
2018.01.27 05:00:10.765 Core 1  authorized (agent build 1755)
2018.01.27 05:00:10.768 Tester  EURUSD,M1 (MetaQuotes-Demo): testing of Experts\Examples\MACD\MACD Sample.ex5 from 2017.09.01 00:00 to 2018.01.26 00:00

2018.01.27 05:00:23.217 Core 1  MetaTester 5 started on 127.0.0.1:3000

2018.01.27 05:00:23.217 Core 1  46 Kb of total initialization data received
2018.01.27 05:00:23.217 Core 1  Intel Core i7-6700  @ 3.40 GHz, 8073 MB

2018.01.27 05:00:23.217 Core 1  EURUSD,M1 (MetaQuotes-Demo): generating based on real ticks
2018.01.27 05:00:23.217 Core 1  EURUSD,M1: testing of Experts\Examples\MACD\MACD Sample.ex5 from 2017.09.01 00:00 to 2018.01.26 00:00 started with inputs:
2018.01.27 05:00:23.217 Core 1    InpLots=0.1
2018.01.27 05:00:23.217 Core 1    InpTakeProfit=50
2018.01.27 05:00:23.217 Core 1    InpTrailingStop=30
2018.01.27 05:00:23.217 Core 1    InpMACDOpenLevel=3
2018.01.27 05:00:23.217 Core 1    InpMACDCloseLevel=2
2018.01.27 05:00:23.217 Core 1    InpMATrendPeriod=26
2018.01.27 05:00:23.217 Core 1  EURUSD : 2017.09.12 23:59 - real ticks absent for 176 minutes out of 1421 total minute bars within a day
2018.01.27 05:00:23.217 Core 1  EURUSD : real ticks begin from 2015.01.01 00:00:00

2018.01.27 05:00:24.537 Core 1  final balance 50168.90 USD
2018.01.27 05:00:24.537 Core 1  EURUSD,M1: 9753093 ticks, 147480 bars generated. Environment synchronized in 0:00:03.140. 
Test passed in 0:00:10.328 (including ticks preprocessing 0:00:01.157).
2018.01.27 05:00:24.537 Core 1  EURUSD,M1: total time from login to stop testing 0:00:13.468 (including 0:00:03.140 for history data synchronization)
2018.01.27 05:00:24.537 Core 1  600 Mb memory used including 44 Mb of history data, 256 Mb of tick data
 

Repeat test - 7 seconds

2018.01.27 05:08:23.818 Core 1  final balance 50168.90 USD
2018.01.27 05:08:23.818 Core 1  EURUSD,M1: 9753093 ticks, 147480 bars generated. Environment synchronized in 0:00:00.077. 
Test passed in 0:00:07.610 (including ticks preprocessing 0:00:01.156).
2018.01.27 05:08:23.818 Core 1  EURUSD,M1: total time from login to stop testing 0:00:07.687 (including 0:00:00.077 for history data synchronization)
2018.01.27 05:08:23.818 Core 1  600 Mb memory used including 44 Mb of history data, 256 Mb of tick data
 
Rashid Umarov:

Result on a home computer. Test time - 10 seconds. HDD

Does BitLocker affect the calculation of Cloud Rating?

 
fxsaber:

Does BitLocker affect the calculation of the Cloud Rating?

The PR (Performance Rating) of an agent depends only on the processing power of the processor core on which it is running. This is described in the Payment section

What is the cost per unit of PR per unit of time?

The cost of work of a testing agent with PR=100 for an hour is set at 0.02 USD. One quantum is taken as a unit of work, which is defined as the work of an agent with PR=1 for 1 ms (1 millisecond). Thus, the cost per quantum is:

QuantPrice=0.02 USD/(100PR*3,600,000 ms)=5.55556E-11 [USD/(PR*ms)]

The table shows the cost of continuous operation for 1 hour and for 1 month of a single-core test agent with PR=100.

Interval QuantPrice, USD/(PR*ms) PR of agent
Time, ms Amount, USD
1 hour
5.55556E-11 100
3 600 000
0.02
1 month
5.55556E-11 100
2 592 000 000 14.40

The optimal number of test agents is equal to the number of cores. If a computer has a processor with 4 cores, 4 agents will be installed by default, and accordingly the cost will be 4 times higher.
.

It is not recommended to set the number of agents higher than the number of cores. It will not increase your earnings, because in this case the PR of each installed agent will drop.

To protect against slow agents in the MQL5 Cloud Network, the time spent by an agent to perform a pass is compared with the time of other agents with the same PR on the same task. This allows you to immediately ban such "slow" agents and do not give them tasks.

Вопросы по оплате в сети распределенных вычислений MQL5 Cloud Network
Вопросы по оплате в сети распределенных вычислений MQL5 Cloud Network
  • cloud.mql5.com
Да, конечно. Мы приветствуем энтузиастов и приглашаем всех желающих создавать проекты по распределенным вычислениям. Чтобы предоставить мощности своего компьютера бесплатно, вам достаточно скачать и установить агенты тестирования. Подробно об этом можно прочитать в разделе Справка. Как происходит учет мощностей, предоставленных моими агентами...
 
Rashid Umarov:

The PR (Performance Rating) of an agent depends only on the processing power of the processor core on which it runs. This is described in the Payment section

To protect against slow agents in the MQL5 Cloud Network, the time spent by an agent to perform a pass is compared with the time of other agents with the same PR on the same task. This allows you to immediately ban such "slow" agents and do not give them tasks.

So your agents (where 21 seconds test) would be banned?