Menu
Sister Sites

Options

Bookmark Thread

First Page First Unread Last Page Last Post

Print Thread

Similar Threads

Metatrader is running slow. Taking 50%CPU 25 replies

EA is using 100% CPU in MetaTrader 4 10 replies

Metatrader using 40% of the CPU all the time when using EA 6 replies

indicator taking up cpu resources??? 3 replies

Metatrader 4 99% CPU Usage 0 replies

MetaTrader is running slow: Taking 100% of CPU

  • Post #1
  • Quote
  • First Post: Edited Jun 16, 2015 3:41pm Jun 14, 2015 6:45pm | Edited Jun 16, 2015 3:41pm
I am running one MetaTrader 4 terminal on a VPS with 20-30 charts open testing various EA settings on a demo account. Seemingly out of no where, my terminal.exe process have become a problem.
One of them " terminal.exe*32" is eating up anywhere from 100,000-120,000K of memory and 100% of my CPU. Oddly enough, if I Close my MetaTrader 4 terminal CPU Usage drops to 1%.
The VPS is running on a quad-core 2.0ghz with 1.0 GB of RAM

1) What could be causing this if its my code? What should I look for inside my code?
2) Is this considered "normal?
3) Are there any software available to fix " terminal.exe*32" process?

I also want to add that
(A) I have Reduced Max bars in history to 1000 and Max bars in chart to 1000
(B) I have Disabled News Feeds
(C) I have Disabled Sound Notifications
(D) I have removed all currency symbols from the Market Watch Panel except for GBP/USD and EUR/USD
Quoting Evasparkling
I am running one MetaTrader 4 terminal on a VPS with 20-30 charts open testing various EA settings on a demo account. Seemingly out of no where, my terminal.exe process have become a problem. One of them " terminal.exe*32" is eating up anywhere from 100,000-120,000K of memory and 100% of my CPU. Oddly enough, if I Close my MetaTrader 4 terminal CPU Usage drops to 1%. The VPS is running on a quad-core 2.0ghz with 1.0 GB of RAM 1) What could be causing this if its my code? What should I look for inside my code? 2) Is this considered "normal? 3) Are...

Its not, i have several comps with different things running, after updating 840, tried search forums, didnt find any solution yet,
will post here if find.
Try setting the processor affinity to one processor only.
go to user -> appdata-> local -> virtual store and find your broker metatrader folder and check its size. if you do backtest for many times lots of GB/s cash stored in here find them and clear them. hope it wil be sloved.
Similar problem - shortly after a post 2014 new build update.

Check log file for size - can fill 1 TB in no time.

Location of the MT4 log files.

File → Open Data Folder → etc, etc.

This illustration relates to Windows 8.1 64 bit. Folder and file paths for Windows 8.1 32 bit and other versions of windows may or will need to be changed accordingly.

  1. C:\Users\Your user name\AppData\Roaming\MetaQuotes\Ter minal\32 character alphanumeric terminal identity\logs\
  2. C:\Users\Your user name\AppData\Roaming\MetaQuotes\Ter minal\32 character alphanumeric terminal identity\tester\logs\
  3. C:\Users\Your user name\AppData\Roaming\MetaQuotes\Ter minal\32 character alphanumeric terminal identity\MQL4\Logs\

​If more that one MT4 / MT5 Terminal is installed the associated Terminal can be found via >> 32 character alphanumerical terminal identity >> original.txt.
The original.txt file will contain the Broker name and whether MT4 or MT5.

The below link provides a temporary solution to keep things up a running till the source of the problem can be located and solved. It may or may not be temporary useful depending ​on particular case.

​For remainder see this post >> http://www.forexfactory.com/showthre...92#post7669992

TSLA 123.18 30-Dec-22 [180.13 46.23% Fri 17-Mar-23]
How about the indicators and/or EAs?
Maybe one of them is bad coded or not compatible with your MT.
Using the RobotFX EAs for a while https://www.robotfx.org/
  • Post #7
  • Quote
  • Last Post: Sep 4, 2015 7:12am Sep 4, 2015 7:12am
Quoting wattaman
How about the indicators and/or EAs? Maybe one of them is bad coded or not compatible with your MT.
Probably the most common cause. The problem in my case was code not compatible with post 2014 new build code changes but I cannot comment on other cases.
TSLA 123.18 30-Dec-22 [180.13 46.23% Fri 17-Mar-23]
0 traders viewing now