Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sat, 18 May 2024 19:51:16 +0000
[Locked] - Infrastructure Upgrades
View Count: 613
| [2024-01-17 00:18:14] |
| Sierra_Chart Engineering - Posts: 14423 |
|
It is important for us at Sierra Chart to have redundancy for all of our services that we offer. This means, that if there is a failure with one system, whether this is hardware or software related, that there is another system, available to perform the same function. Redundancy, is something that we always have but there are a lot of systems and services we have, and there still is areas where redundancy can be improved. And there may be some areas, where there is no redundancy. For example with EUREX, there is a limited redundancy. Since the redundancy is very expensive. Close to €10,000 per month for additional redundancy. We will get back to EUREX in a moment. Since we do have a solution to improve redundancy that should not cost us more but this is yet to be determined. For systems, that are not considered by us to be mission-critical there is no redundancy. For example our C++ custom studies build server there is just one build server. If there is a problem, builds will fail. There was a recent issue with the build server, and we are going to be adding another build server. And the cause of the problem last time, has been determined and there are changes made which prevents it from occurring again. It had to do with a conflict between the 32-bit and 64-bit MinGw compiler. The 32-bit compiler is now removed. For our web services which includes the website, Sierra Chart logins, and support systems, there is redundancy. Currently we have triple redundancy with this but we will take this to quadruple redundancy. The redundancy that we have now with web services is much better than it was previously. However, the Sierra Chart desktop program can still be used even without our web services being available. This has been the design for about 20+ years. We are going to implement, with all of our web services, which even includes things like search and videos and images, and builds, double or triple redundancy. When it comes to market data services, we do have full redundancy. However in the case of what happened at CH1 while everything is a dual redundant there, when the entire data center itself is overheating that is a problem. That would impact US stock data, CFE and NASDAQ global indices and NASDAQ TotalView. We will always have redundancy with these services but there still can be a point of failure which can affect these. This is going to be hard for us to work around until the services, have a much higher level of demand. For CME Group data and order routing, we do have redundancy but we are going to be expanding upon this and improving it further. CME order routing has triple redundancy already. Now if the CME Aurora DC3 data center were to run into a cooling problem and threaten all of its systems to the point where the systems are inoperable, then there is going to be a problem and order routing will become unavailable. This is unlikely but it is something to consider. With crypto currencies, we do have full redundancy, but we did not have redundancy with Binance because of the restriction of not being able to access market data outside of the US. We have now added redundancy for Binance. ----- EUREX: Now let us get back to EUREX. We are working on a project which we think has high likelihood potential, to ensure there is full redundancy for all aspects of EUREX market data. Update: This project is delayed, due to service provider policy, and ultimately the primary hindrance, is exchange policies and costs. Users have asked us for a long time about EUREX order routing and we intended to do that, but when we saw the cost, and we saw all of the related complexities related to mifid compliance, and the trouble in the world, it just became something that was too burdensome and something which would cause us to be losing money for a small amount of users. If someone is interested with financial and technical related help, related to EUREX order routing, then please do contact us. So if there is people who really want us to do direct EUREX order routing in Frankfurt which we can certainly do well, and you can help us with support and cost, then we might be interested. Contact us through a support ticket: https://www.sierrachart.com/UserControlPanel.php?page=SupportTickets ----- Quality Engineering comment: At Sierra Chart, we are very anti-woke. We do things in a very serious traditional, careful, solid manner at all times. We can always be trusted for this. This is what bring stability, and is why we are going to be investing more money, and resources over the next 3 to 4 months, to greatly improve our hardware infrastructure. In the world of software, we see this direction towards total lunacy and absurdity. There simply is no other way to describe it. Sierra Chart will always be traditional and solid and not in the direction of lunacy. For example, the mentality, that a scroll bar to scroll through the content of a window is no longer useful and should not exist or should be a tiny object which is impossible to effectively interact with, and effectively useless, is the ultimate in stupidity. And it does not matter what anyone thinks. The scrollbar has a use. It is a single dedicated object that performs a specific purpose dedicated for the purpose of scrolling through content of a window. It must be visible. The width of it must be adjustable. If you do not want it, then there can be an option in the user interface to disable it. If you want it less wide, there can be an option in the user interface to control this. Software developers who decide to remove it or automatically hide it, or make it dramatically less wide to the point of un-usability with no ability to readjust, are engaging in crimes against humanity. We mean that. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2024-02-11 06:27:34
|
| [2024-02-11 02:33:01] |
| Sierra_Chart Engineering - Posts: 14423 |
|
In the thread, about the overheating situation at CH1 in Chicago in January 2024 we mentioned that we are considering leaving Chicago and relocating to Michigan. Or possibly Franklin Park (outside of Chicago).: Resolved: Data Center Notice for CH1: Data Feeds Affecting! Please read! We want to update this thread, and confirm that we are definitively 100% leaving Chicago with servers and networking equipment. We are removing all of our servers and networking equipment from Chicago and will be relocating to Southfield Michigan. We expect this will be completed, no later than June 2024. The process is not likely to begin until April at the soonest. The facility we will be going to, in Southfield Michigan is absolutely superior compared to CH1 in every way. It is a much easier facility to work in and more accessible for us. They literally have their own supply of power out of Ohio. They have their own substation. They have sufficient backup generation that can run indefinitely on natural gas. We are glad to be leaving Chicago, and Equinix, terrible to work with, and the detrimental location of Chicago. There is not going to be any degradation of service, only an improvement. Latency will not be affected. That has already been analyzed. We will have a 100 Gbs fiber dedicated connection between our new location space in Southfield Michigan to/from Chicago to receive exchange feeds. To be clear, connectivity will be redundant. We will still maintain servers in Aurora Illinois for CME order routing and CME market data processing. Aurora will still be a redundant, low latency and secure location for order routing. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2024-02-11 02:59:02
|
| [2024-02-11 02:37:06] |
| Sierra_Chart Engineering - Posts: 14423 |
|
---- Denali Data Feed: Starting last week, starting to February 2, 2024, we have had some users in Europe reported degradation with the Denali Data Feed. First we want to make it very clear, there is no problem, with our source data feeds for the Denali Data Feed which originate from the exchanges. There is no problem with the market data processing. This is all very efficient. There is no problem with our servers. There is no problem with our network equipment. There is no problem with our network connectivity. There is no problem with our ISP Cogent, in Chicago or the United States. Everything is working perfectly. There are no issues with degradation of data delivery within the US, or in the Asia-Pacific area. This is strictly a problem some users have in Europe only. The primary way we are going to address this, is adding an additional ISP and also reporting the issue to Cogent. This new ISP, will be in our new location space in Michigan. This location should become initially operational in about a month. Refer to this help topic, to the extent you can resolve this yourself: Prices / Data Falling Behind: 4.12 - Sierra Chart Exchange Data Feeds ----- One of our users in Portugal, has raised issues receiving the Denali Data Feed, on February 2, 2024. Their graphs showed Cogent all the way to their ISP. From our side, we show Cogent and Tata Communications. See below. So the return packet acknowledgments which are essential for the data flow from the Sierra Chart network to their computer are taking a different route. The problem could be with Tata Communications. Tracing route to po1-84-90-251-139.netvisao.pt [84.90.251.139] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.10.20.4 2 * * * Request timed out. 3 1 ms 1 ms <1 ms be2051.ccr41.ord03.atlas.cogentco.com [154.54.84.49] 4 1 ms 1 ms 1 ms be2766.ccr42.ord01.atlas.cogentco.com [154.54.46.177] 5 7 ms 7 ms 7 ms be2718.ccr22.cle04.atlas.cogentco.com [154.54.7.130] 6 19 ms 19 ms 19 ms be2890.ccr42.jfk02.atlas.cogentco.com [154.54.82.246] 7 19 ms 19 ms 19 ms be3295.ccr31.jfk05.atlas.cogentco.com [154.54.80.2] 8 18 ms 18 ms 18 ms tata.jfk05.atlas.cogentco.com [154.54.12.18] 9 * 119 ms 120 ms if-ae-32-3.tcore2.ldn-london.as6453.net [80.231.20.106] 10 * * * Request timed out. 11 119 ms 119 ms 119 ms if-ae-19-2.tcore1.sv8-highbridge.as6453.net [80.231.138.21] 12 117 ms 117 ms 118 ms if-ae-1-3.tcore1.pv9-lisbon.as6453.net [80.231.158.29] 13 117 ms 123 ms 123 ms if-ae-2-2.tcore2.pv9-lisbon.as6453.net [80.231.158.6] 14 110 ms 110 ms 111 ms 80.231.159.46 15 111 ms 110 ms 110 ms 10.170.128.5 16 112 ms 112 ms 112 ms pa1-84-91-1-222.netvisao.pt [84.91.1.222] 17 * * * Request timed out. 18 * * * Request timed out. ---- For Cogent to troubleshoot this type of an issue they require at the time of an incident both a ping and a trace route in both directions. It is difficult for us to gather this information for individual users when there is a problem. What we are going to do, is in our new colocation space in Michigan, we are going to add a Web server there for you to be able to run ping and trace route, from that location to your IP. Then you can gather all the information and give it to us and then we can give it to Cogent or other ISPs whichever one is being used. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2024-02-11 04:42:58
|
| [2024-02-11 06:25:40] |
| Sierra_Chart Engineering - Posts: 14423 |
|
Actually even better regarding this: What we are going to do, is in our new colocation space in Michigan, we are going to add a Web server there for you to be able to run ping and trace route, from that location to your IP. Then you can gather all the information and give it to us and then we can give it to Cogent or other ISPs whichever one is being used.
We will build this functionality into our real-time server and then in Sierra Chart you can select a command from one of the menus to signal the real-time server to create this information and return it back into the Message Log. 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, use the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: