Virtual hosting in MetaTrader 4/5 platforms and data security - page 7

 
joo:
There is a minimal understanding. And I have read the articles. But this is why questions arise, because the article spoke about dynamic downgrading the priority of the EA (which means that there is nothing to be afraid of - the server will not let itself be suspended anyway), but on the other hand, you say that voracious EAs will be blocked and "there is no need to be cheeky". So does dynamic downgrading work or not?
It's probably time to get hosting and check it out. Otherwise you can keep asking questions like this indefinitely.
 
joo:
I have a minimum understanding. And I have read the articles. But this is why I have questions, because the article describes dynamic downgrading of the corresponding EA (which means that there is nothing to be afraid of - the server will not let itself be suspended anyway), but on the other hand, I'm told that the voracious EA will be blocked and there's "no need to get impudent". So does dynamic downgrading work or not?

I have detailed everything, including downgrading the priority, sending out soft limit notifications and then stopping at the hard limit.

Right now we are working with resource control, including notifications on MetaQuotes ID and collecting statistics in order to set the limits correctly.

 
barabashkakvn:
It's probably time to get hosting and check it out. Otherwise you can keep asking questions like this forever.

Exactly.

He's got 24 hours of free testing and he hasn't even tried to test it :)

 
Renat:

Exactly.

He has 24 hours of free testing and he didn't even try to check it :)

Tried to, didn't work. That was in the early days of the service and on 4. Didn't try again, because I need it for 5 anyway, and it's impossible to "check" for it.

And even when such an opportunity arises, I still can not try:

The first reason is that the indicator (standard) calculates more bars in history than the value set for the chart. I do not understand why.

2. The function of creating a handle for an indicator and its deletion in the EA during charting, but it does not work in the tester. It clogs all available memory and hangs the system. I do not understand why.

Service Desk is silent. The error is critical and he is silent.

How can I try it if something that should work does not work?

And the notifications on MetaQuotes ID do not work.

 
joo:

Tried to, didn't work. That was in the early days of the service and on 4. Didn't try again, because I need it for 5 anyway, and it's impossible to "check" for it.

Try it now.



And then offtopic:

And even when such an opportunity arises, I still can not try:

The first reason is that the indicator (standard) calculates more bars in history than the value set for the chart. I do not understand why.

Output the number of available bars to the log.

If in the tester, it's clear - it gives bars with a reserve. If in the main terminal, the accumulated new bars do not shift the history, because it would lead to disastrous consequences for indicators and Expert Advisors. That's why history accumulates - it's always been that way for 15 years.


2. My Expert Advisor works on a chart by creating a handle for an indicator and then deleting it, but it does not work in the Strategy Tester. It clogs all available memory and hangs the system. I do not understand why.

Service Desk is silent. The error is critical and it's silent.

How can I try if something that should be working doesn't work?

The ticket was just created yesterday and its turn has not come to me yet.

But when you create 4,500 custom indicators, you should think about the fact that they are built into the calculation model of the terminal, they become a shared resource and require careful handling. The terminal does not instantly delete the calculated indicators.

 
joo:

And notifications on MetaQuotes ID do not work.

Prove it technically, please.

In today's incomplete day, traders have successfully sent over half a million push messages via MetaQuotes ID. Personally, I receive several dozens (sometimes up to a hundred) messages every day.

 
Renat:
Try it now.

"Highlight virtual server" - not active for demo accounts. And for real accounts there is no such item in the menu at all.

And then offtopic:

Output the number of available bars to the log.

If in the tester, everything is clear - it gives bars with reserve. If in the main terminal, the accumulated new bars do not shift the history, because it would lead to disastrous consequences for indicators and Expert Advisors. That's why history accumulates - it's always been that way for 15 years.

When setting "max bars in the window" in the terminal settings, for example 1000, we expect that the indicator in this window will not calculate more than the specified value. Why else would this feature be useful? No, the indicator calculates all of the history on the HDD.

The ticket was just created yesterday and it has not come to this point yet.

But when you create 4 500 custom indicators, you should think about the fact that they are built into the calculation model of the terminal and they should be treated with care.

If there were 4,500... So, one cannot create and delete normally. On the chart it can, but not in the tester.

It's expected, at least, that code running on a chart will work the same way in the tester (I'm not talking about identical trading results, and I'm not talking about alerts, sound playback and slips). The work of the code should be identical. There is no way to test anything now, the Expert Advisor will not work on the hosting.

 
Renat:

Prove it technically, please.

In today's incomplete day, traders have successfully sent over half a million push messages via MetaQuotes ID. Personally, I receive several dozens (sometimes up to a hundred) messages every day.

I was happy to provide all the technical details to the MQ specialist in personal correspondence. Pushys are working unstable. A few days ago they stopped working at all. I've blamed it on a lot of things, both innocently killed processes by killer, and bad firmware... Few days ago I purposely uploaded to the phone the clean firmware with which the pushers worked - no, they don't. I will provide any proof again to your specialists on request - no problem.
 
joo:

"Highlight virtual server" - not active for demo accounts. And for real accounts there is no such item in the menu at all.

Click on the currently active trading account, not on any inactive one. It is necessary, as the account data is necessarily used.

Everything works fine on demo accounts, there are no limitations.


What I mean is that when setting "max bars in the window" for example 1000 in the terminal settings, the indicator in this window is expected to calculate not more than it is set. Why else would this feature be useful? But no - the indicator calculates all of the history that lies on the HDD.

You are confusing something or worse. Without evidence and especially since you don't name the exact number of records on the drive (maybe there are 1100 records).


If it were 4500... So one normally created and deleted can not. In the chart it can, but not in the tester.

You cited test code to create 4,500 custom indicators. I explained that the indicators are not deleted instantly and this could lead to a memory shortage.


It's expected, at least, that code running on a chart will work the same way in the tester (I'm not talking about identical trading results, and not talking about alerts, sound playback and slips). The work of the code should be identical. There is no possibility to check anything now - the Expert Advisor will not be able to work on the hosting.

You forget the technical details, but you are very generous with critical conclusions.

If your EA behaves similarly to the "I will create a thousand independent indicators" example, you'd better reconsider your approach to analysis. For example, use the function of calculation of the indicator built into the Expert Advisor on a short data section, instead of running an expensive and independent indicator.

The indicator (especially custom one) is an expensive, independent, long-term calculation unit, which is created specifically for long-term use. It is expensive to create, then it works quickly for the entire data interval, and it is also expensive to delete at the end. The option "create and immediately delete" is fundamentally wrong in relation to indicators.


It's all an offtopic. Create separate threads if you want to discuss your expert, please.

 
Renat:

Click on the currently active trading account, not on any inactive one. This is necessary, because it is mandatory to use the account data.

Everything works fine on demo accounts too, there are no restrictions.

Yes, that's what I'm doing - inactive.

You are confusing something or worse. Without evidence and especially since you don't name the exact number of records on the disk (maybe there are 1100 records).


You cited test code to create 4,500 custom indicators. I explained that the indicators are not deleted instantly and this could lead to a memory shortage.

There are over 200000 bars on the disk. At least if Bars() does not lie.

If the "I will create thousands of independent indicators" behavior is similar in an Expert Advisor, you should reconsider your approach to analysis. For example, use the function of calculation of the indicator built into the Expert Advisor on a short data interval, instead of running an expensive and independent indicator.

The indicator (especially custom one) is an expensive, independent, long-term calculation unit, which is created specifically for long-term use. It is expensive to create, then it works quickly for the entire data interval, and it is also expensive to delete at the end. The option "create and immediately delete" is fundamentally wrong in relation to indicators.

I wrote that I create only one instance of an indicator. "The"I will create and immediately delete" option is fundamentally wrong with respect to indicators. "This is exactly what the optimizer does. And there is nothing wrong with it. The user should not do the same - create an indicator, take the data, delete the indicator.

This is all an offtopic. Create separate branches if you want to discuss your expert, please.

I wanted to be useful. OK, I won't do it again.