View Full Version : Currency Server API

Finsys Technical
01-31-2014, 07:54 AM

We used third party data feed api using Currency Server API 10, We are getting feed really fast when we test it using client utility come with API on same PC but once we connect it remotely by using API from any Pc outside feed start delaying. Kindly let us know how to resolve this issue, we even shift our Server which is getting data feed and our BO server in same data center but still it did not help.


01-31-2014, 09:29 AM

It is not supposed to happen any delay, but i need to know how many symbols that you broadcast it's prices, and the frequency of broadcasting and the delay in seconds.

Finsys Technical
01-31-2014, 09:55 AM
92 Symbols, Frequency i cant judge, but delay is around 10 or more seconds

Finsys Technical
01-31-2014, 10:07 AM

This is low latency feed so update is really fast and there are 92 symbols and delay is 10 or more seconds and some time even minute

01-31-2014, 12:17 PM

I think its a network issue, nothing in our API make such delays

Finsys Technical
01-31-2014, 01:30 PM
Should we install it in same machine? or you suggest anything else? i doubt the efficiency if its broadcast from BO to client terminal as well?

01-31-2014, 07:06 PM
Dear Finsys,

Should we install it in same machine? or you suggest anything else? i doubt the efficiency if its broadcast from BO to client terminal as well?

The optimal frequency for broadcasting 100 symbols prices in the standard servers is around 400~500 ms.

But for faster prices (less than 300 ms), there are two parts:

Server side
Client side (client and bo)

You need to improve your server side structure as the following:
We advice you to install your currency server in stand alone server, and you may need to split your main server to two severs, to balance your server side loading. So you need 3 servers, 1 for currency and 2 others for other servers apps. You may start with 2 servers, main and currency and evaluate its performance life with our assistance.

For the client side performance, to be honest you need to check it and tune it. But the factors that affect the client side performance are:
1- number of shown symbols
2- number of open charts
3- if you use tick chart or not

Using these factors you may reach a fair structure with good performance.

You may reach the 100-200 ms Or less
We will let our development department connect to your currency server and give you the best steps.

They will update you soon.

02-01-2014, 06:12 PM

I have to tell that low latency feeds should not necessarily be achieved by fast broadcasting as this would cause sometimes reducing the efficiency instead of improving it and hence worst results. Otherwise you could have increased the broadcasting time in the default DDE setup and without bothering yourself with API development but this is not a solution to reduce latency.

Low latency feeding in principle can be achieved by replacing the technique from DDE to API based feed. This concept should do perfect results by itself as you read prices API-to-API which is much faster than DDE. The latency in DDE is not the broadcasting time itself but the technique as reading data by DDE is slow.. So if you change to API and kept the broadcasting time to itself 300-400 ms should show perfect results.

This broadcasting time is very fast and any trader can not distinguish 300ms from 20ms. Besides, Robots or EA's which might be more sensitive are also controlled in the backend by smart dealers and bridges which also should correct any possible scalping.

Hope this helps.