Why are there so few experts in the MQL5 database? - page 11
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
Going to buy a computer with a lot of cores. I don't really care what kind of Windows operating system it will have (32 or 64 bit), but in terms of MT5 performance which one is better: 32 or 64 bit? Or is there not much of a difference?
Windows is 64-bit... It's good. Matlab 64-bit runs like a tractor. Except the MT processor isn't suitable?
What version of the installer should it be? The one I'm downloading is 5.0.0.281.
I'm not sure exactly, but I suspect that Win 64 may easily fit into 32 Bit platform as well (I can't say about Matlab)...
What may be the case here is that both OS and Matlab understand it and work with what you have, but what and how MT will do in the 32 Bit process is the big question...
PS
The question is also related to the fact that I seem to have somewhere Win XP for 64 Bit, but I'm not sure about the availability of a suitable CPU...
Try downloading the installer again fromhttps://download.mql5.com/cdn/web/metaquotes.software.corp/mt5/mt5setup.exe - the version may have been taken from the browser/proxy cache. Clean the caches and try again.
Older versions of the installer were only locked to 32 bits.
I recommend Windows 7 x64 and more cores with memory.
Not exactly sure, but I think Win 64 can easily fit a 32 Bit CPU....
Something does not impress the 64-bit version of the tester. I ran the test of the same Expert Advisor with the same parameters on the 32- and 64-bit tester. The result is that it takes one and a half times longer on 64- than on 32-.
32-bit:
2010.07.09 23:32:52 Core 1 Opening Errors: 0 Closing Errors: 0 Modification Errors: 0 Requotes: 72010.07.09 23:32:52 Core 1 Running time: 13 min. 51 sec.
2010.07.09 23:32:52 Core 1 PriceChannel_multi Expert Advisor has finished its work on EURUSD chart, H1 period
2010.07.09 23:32:52 Core 1 EURUSD,H1: 6339400 ticks (3171 bars) generated within 810238 ms (total bars in history 9318)
64-bit:
2010.07.09 23:54:58 Core 1 Opening errors: 0 Closing errors: 0 Modification errors: 0 Requotes: 6
2010.07.09 23:54:58 Core 1 Running time: 20 min. 52 sec.
2010.07.09 23:54:58 Core 1 PriceChannel_multi Expert Advisor has stopped working on EURUSD chart, H1 period
2010.07.09 23:54:58 PM Core 1 EURUSD,H1: 6339383 ticks (3171 bars) generated within 1223718 ms (total bars in history 9318)
A new build is out today - we'll run more speed tests on it.
So far the 64bit version of build 291 from July 1 has been downloaded and has some bugs.
Something does not impress the 64-bit version of the tester. I ran the test of the same Expert Advisor with the same parameters on the 32- and 64-bit tester. The result is that it takes one and a half times longer on 64- than on 32-.
The current build of the 64-bit version of the tester had optimization problems causing lags in comparison to the 32-bit version.
This has now been fixed and in the next build the x64 speed is even faster than the 32 bit version.
Yesterday and today the terminal crashed and crashed ten times when trying to start testing.
I noticed it but did not have enough time to check it and understand that it happened at the moment when the Expert Advisor was addressing a non-existing array element.
I cannot understand if this is related to the 64-bit version of the tester or just an accident. I had errors when accessing arrays earlier too, but the terminal did not crash but simply stopped testing.
Yesterday and today the terminal crashed and crashed ten times when trying to start testing.
I noticed it but did not have enough time to check it and understand that it happened at the moment when the Expert Advisor was addressing a non-existing array element.
I cannot understand if this is related to the 64-bit version of the tester or just an accident. I had errors when accessing arrays earlier too, but the terminal did not crash but simply stopped testing.