Login Page - Create Account

Support Board


Date/Time: Sun, 24 Nov 2024 16:25:38 +0000



Post From: poor connection

[2024-05-22 11:27:12]
User512353 - Posts: 42
I have the same problem here, intermittently showing up since May 6 (not every day).

My observations during RTH:

- Charts suddenly stop updating, but this typically effects NOT all the symbols in a chartbook. So, other symbol's charts keep updating. This indicates that there is no network error, but hints to a server CPU capacity problem.

- The problem typically occurs when there is a large number of transactions for the symbol at the exchange, e.g. for ESM4. This also hints to a server CPU capacity problem.

- A concurrent ping to ds12.sierracharts.com (38.103.112.181), which is one of the involved data servers that reconnects, reports a whopping 30% packet loss during RTH. This is not only during the time that charts freeze, but a common observation during RTH. This again hints to a server CPU capacity problem, because the round trip times are pretty constant and not different from ETH. (There is no packet loss during ETH.)

Do you monitor the data server CPU capacity?
Do you monitor connection losses / reconnects of the data servers?

I strongly suggest to review the data server behavior. If there is no CPU capacity shortage, you should look for contention in the software stack. That's all I can currently say from here with my 30 years IT experience in server hardware, firmware, OS, and software R&D.

The problem should be looked at, because these problems seriously affect trading.

It would also be desirable to have more debugging aids at hand for these problems. These should be built into the SC software. A standalone debugging tool may also be helpful to cut off SC software problems. Plus some kind of dashboard for the server status, e.g. like IBKR implements in TWS.