Topics
Replies
Spotware
09 Sep 2014, 14:15
RE:
rkokerti said:
Dear Developers,
I continued the analysis of my indicator, to find the reason of huge CPU consumption.
I think I found the reason. If I remove the attached part of the code, then CPU consumption greatly reduced.
ATRValue = Math.Round(atr.Result[index] *10000 *(Symbol.PipValue / Symbol.PipSize)); PosPerc = Math.Round((ATRValue / Account.Equity *100),1); ChartObjects.DrawText("ATR",ATRValue.ToString() + " $" + "=" + PosPerc.ToString() + " %",index+2,MarketSeries.Close[index],VerticalAlignment.Center,HorizontalAlignment.Right,Colors.MediumSpringGreen);Unfortunately, I need this code snippet, because this is the part of my Risk Management.
Another observation is that if there is no open position then CPU consumption low, otherwise very high.
There is something proposal how to solve this problem?
Instead of calculating those values on every tick (in OnCalculate method) we can recommend you to use OnTimer event. You put this code to OnTimer handler and try to adjust the timer interval.
@Spotware
Spotware
08 Sep 2014, 10:21
Dear Trader,
We convert Quote to Home using rates at the time you run the backtesting. We do not plan to change this functionality in the future. We can recommend you to post an idea to vote.spotware.com. If it collects enough votes, we will consider to implement it.
@Spotware
Spotware
08 Sep 2014, 09:26
These workspaces are not showing up on Ctrader Web though. Ctrader web is showing an old workspace I set up a while back - but non of the new workspaces from the desktop.
cTrader Web and cTrader Desktop do not share set of workspaces, the applications work independently.
@Spotware
Spotware
05 Sep 2014, 09:45
RE: RE:
oguti said:
I don't think so.
If you close the cTrader without log in, when you open a new session cTrader load the last saved Workspace, not the last one used. I just checked.
Spotware said:
Your workspace is saved automatically when you exit cTrader so you always have the last workspace you worked at, saved.
Workspaces is a cTrader ID feature. As long as you are connected to your cTrader ID your current workspace is automatically saved, and your last used workspace is always applied. Please always be logged in to your cTrader ID if you want to use the feature.
@Spotware
Spotware
03 Sep 2014, 17:07
if (position != null && position.StopLoss != 0 && position.TakeProfit != 0 && position.Comment == Strategy1)
You need to check SL and TP for null instead of comparing it with 0.
You can also use Visual Studio to debug your algorithms: http://help.spotware.com/calgo/visual-studio/debug-cbots
@Spotware
Spotware
03 Sep 2014, 17:00
Our tests show that there is no any significant difference between CPU consumption in cAlgo 1.23 and latest cAlgo 1.24. Probably performance issues that you observe do not relate to the latest update.
We deployed latest version to all our brokers. Different CPU consumption for different brokers could be caused because of different price feeds. For example, if broker provides ticks more frequently your indicators and cBots will require more CPU resources to handle all incoming ticks.
@Spotware
Spotware
03 Sep 2014, 16:20
RE: RE:
jdaerial said:
Hi Spotware,
I only use trendlines and Stochastics - and do have a number of charts up.
I think the cloudspace should be able to hold all this info in the future - most people I'm sure would use multiple pairs.
Thanks
Spotware said:
We are investigating the issue. It looks like your workspace is too big to be saved in the cloud. You can try to close several charts and indicators.
Can you save a workspace will less amount of charts? We will increase the available space in the near future.
@Spotware
Spotware
03 Sep 2014, 10:04
Order is fixed: open, high, low, close.
Backtester fills limit orders by target price or better. Stop orders could be filled by worse price.
Example 1.
- Place Buy Limit order at 1.2345
- Next tick: Ask = 1.2320
- Order will be filled by 1.2320
Example 2.
- Place Buy Stop order at 1.2345
- Next tick: Ask = 1.2350
- Order will be filled by 1.2350
@Spotware
Spotware
09 Sep 2014, 14:27
cServer doesn't have any throttling logic.
We prepared several performance optimizations in cAlgo 1.25. If it is possible please check how your cBots will perform in cAlgo 1.25. Currently cAlgo 1.25 is deployed for Spotware environment only:
http://spotware.ctrader.com/calgo-spotware-setup.exe
@Spotware