A minute and a half difference between local time and fresh tick time. What to do. - page 8

 
pivomoe:

And what does this have to do with 90 second delays ? Are the figures the same order of magnitude ?

Read at your leisure (But only from the beginning)

https://www.mql5.com/ru/forum/38456

By the way, where do you live and what ISP do you have?
ФОРТС. Вопросы по исполнению
ФОРТС. Вопросы по исполнению
  • 2014.12.16
  • www.mql5.com
С большими проблемами удалось это сделать (начальник отдела по работе с профессиональными клиентами ДЦ Открытие Евгений Сергеевич,.
 
pivomoe:

What do you need to do? Beat it yourself?

Use a TS where you don't have to 'save' anything

 
prostotrader:

Read at your leisure (But only from the beginning)

https://www.mql5.com/ru/forum/38456

By the way, where do you live and what ISP do you have?

SPb. The ping to MICEX is less than 90 seconds if that's what you mean.

 
pivomoe:

SPb. The ping to MICEX is less than 90 seconds if that's what you mean.

I see...

Change your provider (I have OnLime (100/100) Moscow).

2019.03.20 19:28:11.571 Trades  'xxxxx': modify order #101433221 sell limit 1.00 MTSI-9.19 at 27292 sl: 0 tp: 0 -> 27260, sl: 0 tp: 0 placed for execution in 5.073 ms
2019.03.20 19:28:11.690 Trades  'xxxxx': cancel order #101433221 sell limit 1.00 MTSI-9.19 at 27260 placed for execution in 6.303 ms
2019.03.20 19:28:14.005 Trades  'xxxxx': modify order #101432932 buy limit 5.00 GBPU-9.19 at 1.3125 sl: 0.0000 tp: 0.0000 -> 1.3127, sl: 0.0000 tp: 0.0000 placed for execution in 7.284 ms
2019.03.20 19:28:28.689 Trades  'xxxxx': buy limit 5.00 PLT-9.19 at 873.7 placed for execution in 6.721 ms
2019.03.20 19:28:28.731 Trades  'xxxxx': cancel order #101433356 buy limit 5.00 PLT-9.19 at 873.7 placed for execution in 6.132 ms
2019.03.20 19:28:36.511 Trades  'xxxxx': buy limit 2.00 ED-12.19 at 1.1176 placed for execution in 7.859 ms
2019.03.20 19:28:36.512 Trades  'xxxxx': sell limit 2.00 ED-12.19 at 1.1869 placed for execution in 7.884 ms
2019.03.20 19:28:36.644 Trades  'xxxxx': modify order #101433362 buy limit 2.00 ED-12.19 at 1.1176 sl: 0.0000 tp: 0.0000 -> 1.1178, sl: 0.0000 tp: 0.0000 placed for execution in 6.599 ms
2019.03.20 19:28:36.644 Trades  'xxxxx': modify order #101433363 sell limit 2.00 ED-12.19 at 1.1869 sl: 0.0000 tp: 0.0000 -> 1.1867, sl: 0.0000 tp: 0.0000 placed for execution in 7.100 ms
2019.03.20 19:28:36.772 Trades  'xxxxx': cancel order #101433362 buy limit 2.00 ED-12.19 at 1.1178 placed for execution in 6.260 ms
2019.03.20 19:28:36.775 Trades  'xxxxx': cancel order #101433363 sell limit 2.00 ED-12.19 at 1.1867 placed for execution in 8.514 ms
 
prostotrader:

I see...

Change your provider.

Moscow ?

 
pivomoe:

Moscow ?

Yes

Added

If you have a friend in Moscow, then ask him to install MT5, and control

will be through TeamViewer

 
prostotrader:

Yes

Added

If you have a mate in Moscow, ask him to install MT5 and operate it via

You will manage it via TeamViewer.

While I am solving the problem with tens of seconds, you are talking about tens of milliseconds. Why do you withdraw orders so often? Are you freeing up margin?

 
pivomoe:

Don't get distracted )

Have you tried this?

Andrey Khatimlianskii:

3. catch the misses one instrument at a time from one EA. And run 40 Expert Advisors.


But, judging by the fact that the problem is reproduced with a large number of Opera tabs, it really is with the network.
Perhaps, the terminal lacks some resources.

 
Andrey Khatimlianskii:

Don't get distracted )

Have you tried that?


But judging from the fact that the problem is reproduced with a large number of opera tabs, it really is with the network.
Maybe the terminal lacks some resources.

Andrey Khatimlianskii:

Don't get distracted.)

Haven't you tried that?


But judging from the fact that the problem reproduces with a large number of opera tabs, it really is with the network.
Probably, the terminal lacks some resources.

Or, there's an overabundance of them.

 
Andrey Khatimlianskii:

Don't get distracted )

Didn't you try that?


No. Better then to open a second broker's terminal and mine ticks from two servers at once. I am thinking to dig in the following directions:

1. Try to pause if SymbolInfoTick takes a long time to execute.

2. Reduce number of calls on illiquid characters.

3. change windows settings.

I think we should stop at this point. The main thing for me was to get rid of pauses in minutes. I already have a 5 second delay on a hundred characters. (really it's an evening ).

hp Maybe you have any ideas about identifying SymbolInfoTick soon ( refusing to give ticks )