2 second delay execution

Created at 25 Feb 2014, 22:39
How’s your experience with the cTrader Platform?
Your feedback is crucial to cTrader's development. Please take a few seconds to share your opinion and help us improve your trading experience. Thanks!
SN

snowman

Joined 24.02.2014

2 second delay execution
25 Feb 2014, 22:39


I have did only 2 trades with c trader on the desktop version, both entries were 2 to 3 seconds before l got the 

confirmation ticket on the top right side of the platform. l can send you the link the broker gave me for the

download, is it possible they can alter the code or check on the back end before they execute. Use describe

the software as STP processing but that doesn't look like the case with my execution. You know

most brokers don't use STP even though they say.

 

 

 


@snowman
Replies

Spotware
26 Feb 2014, 09:23

With cTrader the brokers cannot "alter the code or check on the back end before they excecute". cTrader is a hosted solution, meaning that the servers are hosted and managed by us (Spotware). The brokers can only configure the servers and there are no configurations that produce delays on excecution.


@Spotware

snowman
26 Feb 2014, 12:14

That's good to know l still haven't did the third trade, My next trade will be on my home pc not the laptop if it does it again l will let us know.


@snowman

Researcher
26 Feb 2014, 12:24

Snowman, in Journal tab you can see actual execution speed in milliseconds including network communication time. You can copy log and post it to the forum.


@Researcher

snowman
26 Feb 2014, 15:34

RE:

Researcher said:

Snowman, in Journal tab you can see actual execution speed in milliseconds including network communication time. You can copy log and post it to the forum.

 

Researcher, l will do that later today it does seem odd that both entries were slow and both exits were fast, when l post it let me know what you think.


@snowman

snowman
26 Feb 2014, 23:16 ( Updated at: 21 Dec 2023, 09:20 )

times

Here is the shot of the execution the times 


@snowman

snowman
26 Feb 2014, 23:17 ( Updated at: 21 Dec 2023, 09:20 )


@snowman

Researcher
27 Feb 2014, 09:52

This is useless, you need to copy content of Journal tab after trade. It looks like this:

27/02/2014 07:51:03.230 | Request to Buy 10 XAUUSD is sent to server
27/02/2014 07:51:03.370 | → Request to Buy 10 XAUUSD is ACCEPTED, order OID1938727 created (27/02/2014 07:51:03.302 UTC+0)
27/02/2014 07:51:03.401 | → Order OID1938727 is FILLED at 1326.64, position PID1279309 (27/02/2014 07:51:03.306 UTC+0)

Here you can see exact time in milliseconds


@Researcher

snowman
27 Feb 2014, 14:53

RE:

Researcher said:

This is useless, you need to copy content of Journal tab after trade. It looks like this:

27/02/2014 07:51:03.230 | Request to Buy 10 XAUUSD is sent to server
27/02/2014 07:51:03.370 | → Request to Buy 10 XAUUSD is ACCEPTED, order OID1938727 created (27/02/2014 07:51:03.302 UTC+0)
27/02/2014 07:51:03.401 | → Order OID1938727 is FILLED at 1326.64, position PID1279309 (27/02/2014 07:51:03.306 UTC+0)

Here you can see exact time in milliseconds

I didn't know that thanks, so when l do a trade l click on the journal tab and that information is there? l did a trade last night it was a bit

faster than the first 2 slow ones and the exit was super fast again. l see the journal has nothing in it now does it erase once l close the platform?


@snowman

Spotware
27 Feb 2014, 14:58

You can find all your journals in Documents/cTrader/Journals folder


@Spotware

snowman
03 Mar 2014, 18:12

I see the information it doesn't reflect what happened l think it was executed at the time in the journal, but the confirmation took a while to get back to the

computer, it might be the laptop l am using not sure. l just did a trade today on my home computer l thought l would try the web version and the entry and exit

were very fast l think l will stick with that for now. 


@snowman

fxMinnow
04 Mar 2014, 10:59

execution speed may be referable to condition of computer.

I`m no problem.

always in sub millisecond.


@fxMinnow