ForexRobotTrader.com robot review - BUSTED! -$3,318

[PipCop]

I am likely going to have to restart this EA test. I was checking on the system today and it appears to have locked up and is otherwise using 100% CPU. I cannot confirm that MetaTrader could function (or was functioning) properly, and was not affecting this EA, so to be fair I will re-create this over the weekend and start fresh.

[Ken Long]

Was this caused by the Steinitz EA. I've been concerned about running this EA, because of the power usage trying to run so many charts at once.

[PipCop]

I cannot confirm that. One thing to keep in mind is the setup I use.

First, each terminal runs Windows XP. I allocate 512MB of RAM to each terminal. In this case, I noticed some slowness a few weeks ago, so I allocated an additional 256MB of RAM to this specific terminal. A few days ago, Windows Update downloaded and installed some patches, but I forced the server to not reboot (I prefer to have reboots done over the weekend, as the server take about 30 minutes to come back up and restart all the terminal machines.) After that I noticed additional CPU usage on the server. Logging into VMWare, I noticed that the FRT machine was non-responsive. I stopped MT and restarted it. Live Updated asked me if I wanted to update. Suspecting a memory leak in MT, I installed the update and restarted MT. However, Live Update demanded to update again and thought it was still on the old version. At that time I tried to shut down the terminal but the OS locked up. Server CPU and HDD usage was high at the time, but still manageable. I logged into the remaining terminals and updated MT with no problems, then forced a shutdown on the FRT terminal and restarted the server. At this point the server has recovered and is using nominal CPU and RAM (about 5% - 10%, which is what I usually see). All terminals are working properly.

As a result, I cannot say the FRT was the cause, but more likely a patch issue, a memory leak in MT, the Vmware client OS (Win XP) having issues, or the likes.

For a user who is running a dedicated WinXP machine, with 512MB of RAM or more, I doubt this will be an issue. My setup is slightly more complex and compounded by the fact that the VMware clients share CPU, RAM and swap on the primary server, so it's hard to compare.

[Ken Long]

The RAM isnt much of a concern on any dedicated home computer. Even an inexpensive laptop nowadays has 1G RAM. And ultimately this may be the most economical way to go.

But I've had concerns about running 24/7 from my home computer. I'm still debating on the choices. The only other option is a VPS service designed for traders.

I havent found a lot of information on the various VPS services that are designed specifically for Forex traders, but there are a few that I know of and they all charge monthly by the RAM needs.

CNS, commercialnetworkservices.com, charges $30/month for a value plan with 384MB RAM, and $65/month for a standard plan with 512MB RAM. This could get quite expensive for a portfolio of EA's, or an EA such as this one that runs so many chart windows. Especially when I'm considering running multiple chart windows per pair. This is one of the liabilities behind multiple pair and multiple EA programs that I havent heard discussed yet. I'm sure it could also apply to any complex EA that has high computing demands.

[ameyhazuan]

Originally Posted by PipCop

I am likely going to have to restart this EA test. I was checking on the system today and it appears to have locked up and is otherwise using 100% CPU. I cannot confirm that MetaTrader could function (or was functioning) properly, and was not affecting this EA, so to be fair I will re-create this over the weekend and start fresh.

Yes, it is because of the EA. It too required alot if graphics processing. What one needs to do is turn off all indicators and put on basic chart i.e: line chart. EA does not need those indicators to be on chart.

Each chart required heavy processing while EA searching for the best entry point . Since this EA depending on multi timeframe, more charts meaning more processing power.

Check your task manager and see if CSRSS.EXE is consuming your CPU. If it does, follow my advice by removing those indicators and leave only basic chart.

[Ken Long]

Thanks that does seem to be the problem. Not just this robot but several I've been testing tend to drain my systems power when actively running, and have frozen my computer several times. I've become very cautious about running them, but this could be the answer.

Some, such as the Demark Lines claim that you need to have the indicator to run the EA. I'll have to test to see if it needs to be attached.

Thanks

[PipCop]

Originally Posted by ameyhazuan

Yes, it is because of the EA. It too required alot if graphics processing. What one needs to do is turn off all indicators and put on basic chart i.e: line chart. EA does not need those indicators to be on chart.

Each chart required heavy processing while EA searching for the best entry point . Since this EA depending on multi timeframe, more charts meaning more processing power.

Check your task manager and see if CSRSS.EXE is consuming your CPU. If it does, follow my advice by removing those indicators and leave only basic chart.

Terminal.exe (MetaTrader) was using 100% CPU, so I've removed the indicators from the charts.

[PipCop]

Originally Posted by Ken Long

Thanks that does seem to be the problem. Not just this robot but several I've been testing tend to drain my systems power when actively running, and have frozen my computer several times. I've become very cautious about running them, but this could be the answer.

Some, such as the Demark Lines claim that you need to have the indicator to run the EA. I'll have to test to see if it needs to be attached.

Thanks

I've found the indicator just has to exist, not be attached to the chart, for most EAs

[ameyhazuan]

Originally Posted by PipCop

I've found the indicator just has to exist, not be attached to the chart, for most EAs

does it solve the problem?

[PipCop]

It appears to have made a big difference. CPU usage is almost nil. The spike is from me logging on.