Support Board
Date/Time: Mon, 25 Nov 2024 18:27:16 +0000
Post From: Sierrachart does not work with OEC
| [2014-02-20 22:45:37] |
| |
|
We also set up enhanced and extended historical data support both for M6EH4 and M6BH4 and can do other symbols as well. One issue users have reported with OEC is a lagging issue, we were spending some time looking into this issue today, and concluded it has to be on the OEC side. Sierra Chart can process over 100 symbols over a FIX connection with no measurable CPU load. It would be a CPU loading problem which would cause a lag on the client-side. But that is not the case here. You are the first person to report a problem with the data feed actually stopping. Clearly an issue like that would be on the OEC side if there still continues to be a heartbeat sent through. And they were sending a heartbeat through, if there was not a reconnection after about a minute. Although we could test this. Maybe there is something wrong with our detection of heartbeats. We will do that now. You had said you lost the connection for 10 minutes. Another issue, we pointed out to OEC, was how historical data requests were counting towards the subscription limit. They did resolve this. Sierra Chart is very well engineered software that is C++ native code. We do not use .NET or prewritten FIX or FAST libraries like OEC does. Therefore, we have confidence in what we offer. Whereas OEC, can have its issues with software components that are not within their control. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2014-02-20 22:47:08
|