MT5 and speed in action - page 42

 
fxsaber:

Thanks for the information. In Benchmark.mqh you need to uncomment the top line and reverse the bottom line. So that it is like this.

Then the metering will work. Now there is a protection, that if "brakes" are detected, then do not measure.

2020.10.05 18:51:57.431 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 31 mсs.
2020.10.05 18:51:58.522 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 19 mсs.
2020.10.05 18:51:59.451 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 18 mсs.
2020.10.05 18:52:00.363 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 13 mсs.
2020.10.05 18:52:01.357 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 18 mсs.
2020.10.05 18:52:02.365 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 19 mсs.
2020.10.05 18:52:03.380 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 18 mсs.
2020.10.05 18:52:04.360 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 18 mсs.
2020.10.05 18:52:05.368 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 18 mсs.
2020.10.05 18:52:06.357 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 13 mсs.
2020.10.05 18:52:07.353 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 21 mсs.
2020.10.05 18:52:08.362 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 18 mсs.
2020.10.05 18:52:09.353 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 12 mсs.
2020.10.05 18:52:10.363 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 13 mсs.
2020.10.05 18:52:11.361 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 13 mсs.
2020.10.05 18:52:12.359 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 12 mсs.
2020.10.05 18:52:13.366 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 19 mсs.
2020.10.05 18:52:14.378 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 13 mсs.
2020.10.05 18:52:15.457 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 14 mсs.
2020.10.05 18:52:16.465 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 20 mсs.
2020.10.05 18:52:17.357 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 29 mсs.
2020.10.05 18:52:18.363 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 13 mсs.
2020.10.05 18:52:19.357 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 18 mсs.
2020.10.05 18:52:20.373 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 90 mсs.
2020.10.05 18:52:21.363 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 15 mсs.
2020.10.05 18:52:22.370 Test VPS (EURUSD,H1)    Alert: Time[Test VPS.mq5 7 in OnTimer: GetMicrosecondCount()] = 12 mсs.

Alertilo, until interrupted.

VPS is the cheapest, with a minimum TP. $2.99/month.

 
A microsecond timer has both a system error and a cost depending on the hardware, operating system and virtualisation.

It does not have 1 microsecond accuracy actually.

We have specifically highlighted the costs and brakes of classic vpsps in articles about our vps service.

Think about overselling the resources of PPS servers when the ISP slices at best 20 Windows systems on one host.

There really are 80% of CPU resources going into system overhead and implicit delays.
 
Renat Fatkhullin:
A microsecond timer has both a system error and a cost, depending on hardware, operating system and virtualization.


Which is what I wrote about earlier in this thread, that there are no brakes on Linux.
Or at least they are very minimal and not noticeable.
But for some reason my posts have been deleted. It's kind of weird.

 
Edgar Akhmadeev:

Alertilo, until interrupted.

VPS is the cheapest, with the lowest TP. $2.99/month.

However, it's a tough case. Snapshot mechanics can only be used bypassed on such machines.

 

Please take the same measurements there.

 

I noticed the following thing, when selecting the server with the lowest ping on your service,
never offers the closest server, always around the corner.
Although previous ping measurements to other servers, I know for sure that the map showed your pps in that area is much closer.
Or is it possible to manually select provider?

 
fxsaber:

However, this is a tough case. Snapshot mechanics can only be used to bypass on such machines.

Of course. For $3 there is nothing to look forward to. Such an option is only for well optimized EAs, without heavy calculations and indicators, with a small number of open positions (so far I have 6-8 positions on each of 4 terminals), with minimal use of functions accessing the server and history, not HF trading (holding time - tens of hours or days). It is enough for me. At first with 12 terminals and non-optimized code I had to spend $50 on the same VPS.

 
Roman:

I noticed the following thing, when selecting the server with the lowest ping on your service,
never offers the closest server, always around the corner.
Although previous ping measurements to other servers, I know for sure that the map showed your pps in that area is much closer.
Or is it possible to manually select provider?

Specify the server name of the broker, please

 
fxsaber:

Please do the same measurements there.

Downloaded your benchmark scripts + example.

  1. On local computer - nothing for 10 minutes
    Benchmark.mqh: TimeAvg[GetMicrosecondsCount()] = 0 mcs.
    

  2. On a heavily loaded virtualized VPS host with multiple terminals in 8 minutes
    Windows Server 2016 build 14393 on Hyper-V, Intel Xeon  E5-2670 v2 @ 2.50 GHz, 40 / 63 Gb memory, 40 / 95 Gb disk, IE 11, RDP, Admin, GMT+1
    
    2020.10.05 20:59:21.344	5555 (EURUSD,H1)	Benchmark.mqh: TimeAvg[GetMicrosecondsCount()] = 0 mcs.
    2020.10.05 21:00:09.343	5555 (EURUSD,H1)	Alert: Time[5555.mq5 7 in OnTimer: GetMicrosecondCount()] = 2 mсs.
    2020.10.05 21:07:22.336	5555 (EURUSD,H1)	Alert: Time[5555.mq5 7 in OnTimer: GetMicrosecondCount()] = 3 mсs
    

  3. On a multi-terminal-loaded physical VPS host in 8 minutes
    Windows Server 2016 build 14393, Intel Xeon  E5-2430 0 @ 2.20 GHz, 33 / 47 Gb memory, 186 / 231 Gb disk, IE 11, RDP, Admin, GMT+1
    
     2020.10.05 21:03:45.228	5555 (EURUSD,H1)	Benchmark.mqh: TimeAvg[GetMicrosecondsCount()] = 0 mcs.
    


Tests were done on a 2630 full terminal, and working VPS terminals are many times less resource consuming and their latencies are known to be lower.

We use workplace hosts of our VPS service.

Files:
5555.ex5  18 kb
Reason: