Remote agents are not working in optimisation (a bunch of x86 computers): what to do ? - page 2
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
With the launch of virtual hosting servers for MT5, we have reassessed the state of our services, including the MQL5 Cloud Network.
It's time to reform the settlement network:
Would a VPN help with this problem?
I'm not really into the subject, but as far as I understand it, it's some kind of local network built over the internet. Will agents be accessible from such a "pseudo-local" network?
The solution is not really a good one.
I, for example, reinstall the system every six months. It's x32 at the moment. Before that it was x64.
And the fact that developers refuse 32-bit system is not good, or rather very, very bad.
Greetings all.
I updated my terminal today, and what a joy, when I ran TC in MT5 for optimization, I got only two on my local cores instead of my usual dozens of optimization threads.
I understand "need to follow development of IT-industry", but the stock of old computers is still very large, it's very reasonable to use them, but in this case it turns out that I was "cut off" as much as I wanted and I'm offered to "move to 64x" ?
Here, I have my computer (Core 2Duo, Win7, x32), and a network in which only one computer is slightly more powerful, and the rest of the pile of computers, mostly on "fourth" stumps and WinXP. This cluster used to do a pretty good job of optimizing. Now, however, it turns out I only have my two cores.
I would like to ask developers what they suggest me to do. How can I use available computing power?
As far as I understand they propose to scrap all computers?
Isn't it too drastic a decision to drop the x32 architecture so abruptly when there are still a huge pile of x32 computers in operation?
Do you often have to reinstall the system, viruses?
You've got a dual core processor, x32 architecture, must be a lot of system crashes? :) CPU or disk, don't you worry about burning it?
Yep, my system too shows processor temperature in red during optimisation so my 8 cores for testing are not
Unfortunately, support for 32bit testers clearly limits our (developers) future because of compatibility.
At the moment there is no point in supporting 32 bit platforms. Yes, 32 client terminals will still be supported, but advanced services will only be on modern platforms.
In 2015, we must move to x64 operating systems, and even more so, forget about XP. If we are talking about serious work.
Renat, with all my respect to MetaTrader - if we are talking about serious development - we should move to WLD, which also works fine on x32 platforms, and at the same time is a head over heels above MetaTrader as a means of TS development.
I would like to ask - what "advanced" services are we talking about for "serious" DEVELOPERS?
Do you often have to reinstall your system, viruses?
You have 2x core processor, x32 architecture, probably the system crashes often? :) CPU or disk, don't you worry about burning it?
Again - there are even single-core Celerons on my network - and none have crashed for several years. And, although each processor is significantly weaker than even my (not at all new) CPU - in terms of number of passes they often do half the total work.
Get rid of compatibility issues with 32/64 bit systems forever by moving to x64 only
I disagree. I have ALL agents that are 32-bit, and they bring very noticeable results
Yes, well, while I see optimization speed decrease by more than 10 times.
I find it difficult to assess the usefulness of this chip - I need testers to optimize TC, but not for earnings.
Sadly. I have to admit that I have a lot of problems now.
I wonder how other developers are doing...
With the launch of virtual hosting servers for MT5, we have reassessed the state of our services, including the MQL5 Cloud Network.
It's time to reform the settlement network: