Support Board
Date/Time: Wed, 27 Nov 2024 10:38:42 +0000
Post From: Denali feed slow during news
| [2023-09-02 10:43:36] |
| Sierra_Chart Engineering - Posts: 17191 |
|
This thread is now locked and kwookoh is now banned from this board. Despite the claims, of users trying to help, you are only creating more burden on us, by posting irrelevant and out-of-date information which has no relevancy whatsoever to the current context. Specifically we are referring to kwookoh. You are creating more burden on us and misleading other users. Ultimately, this is wasting our time and taking away our time, from development and providing effective support to users. It wastes our time because we have to take the time to read through it and explain the situation and explain why it is not relevant. It is actually you who has the misunderstandings. Not us. We will briefly explain why what was posted is not relevant. You posted a thread from three years ago. That particular incident, which lasted a week or two, was the result in network I/O performance improvements, and a different way in which buffering was handled. These network I/O performance improvements did made a major difference in I/O performance for the better but the way in which we handled outgoing data buffering, which was based on an assumption, significantly offset those performance improvements. We then made a further minor change to buffer data, in a structured way, at a single common point before data transmission to the network adapter which then resolved the problem. This change, in combination with a network I/O performance improvements brought a major improvement, to network I/O performance. We also added LZ4 compression which is very fast and reduces bandwidth usage significantly. These changes brought huge fundamental differences with Sierra Chart data feeds for the better. The problems reported before these changes, simply are irrelevant. They have no relevancy to the current context whatsoever. It is not helpful to us to be doing what this kwookoh is doing and ultimately he is being abusive towards Sierra Chart. Not helpful. And that is why we made the decision to ban this user off the board. Despite the illusion, Rui S you are the only one who reported a problem represented by your video, at that time. We have no other reports of the issue but that is not relevant to us since you are reporting, significant issues, repeatedly. We will help you isolate the problem. And we have been contemplating this and we are going to put out a new release, with some diagnostic tools to help us further with this. Allow a few days for that. We are still quite sure, that there is a some other problem, either a local performance issue, or some network communication issue, specific to you, which is leading to the problem. Rui S, clearly, you are having problems which go well beyond, what other users are experiencing. And therefore, when there is an incident, which further investigation, Which may have subsequently be determined to be on our side, then you jump onto that thread and incident and then it associate your much more extensive issues at numerous other times, with that problem. This association is incorrect. We also want to briefly comment on this: Did a side by side comparison. Today it was better. However, I do not think we had the volume surge I've seen before.
The Rithmic feed is much snappier, and updates more frequently. As the end of the video shows, both ladders are set with a 15ms update interval. I always use this because with a 60Hz refresh rate on my displays, anything lower would not be perceivable on my displays (as a 15ms refresh updates theoretically 66 times per second). The NFP in the beginning is pretty well sync'd, but if you look at 33:00, the ISM report which came out 10 seconds later shows a clear latency in the Denali feed (on the right side). What you failed to provide is of how you have this setting set: Sierra Chart Server Settings: Remote Buffer Delay Send Time In Milliseconds (Global Settings >> Sierra Chart Server Settings >> General >> General) We do not know. That makes a huge difference, in the update speed of the Denali Data Feed. One reason we will lock a thread is when there is unnecessary or misleading information being posted, and when this then creates a burden being placed on us, which is no help to anyone. We are being placed under more of a burden by having to read through and respond to all of this and it is helping no one. This week we are going to put out a new version to allow a user to specify both the server address and port to use. This will allow us to have a user connect to a particular server process. We will then increase the heart beat frequency of that process, to every five seconds instead of every 20 seconds. And we will also connect to that same process from a remote location and compare with what we see to what the user sees. We are also going to add two additional fields of information to heartbeat messages. The peak send buffer size, and the time it occurred. We also want to comment on regarding something that kwookoh said about heartbeat messages. When there is a lack of heartbeat messages due to communication being stopped from the server, that information is very helpful to us! And then when these messages return, and then we look at the content of those messages they have important information which is helpful! The Denali Data Feed and other Sierra Chart data feeds are very different today, as compared to the past. We also have a lot more users. Here are some changes which have occurred over the years: -The use of overlapped Network I/O and I/O completion ports for significantly higher I/O performance. - Multiple high-performance Dell R640 servers configured for maximum performance. - 10 Gb networking with 10 Gb Internet connections. These 10 Gb Internet connections do have burst caps and we are increasing these burst caps. We think this was part of, but not completely, the recent issues during extreme market activity but was not a problem, on Friday 2023-09-02. The burst caps were not even are being approached anywhere close. In all cases, network activity was 50 to 70% away from the burst bandwidth cap. These Internet connections can sustain bandwidth, at that burst cap indefinitely. - Data distribution from a single common location, in Chicago CH1. This brings about complete consistency and low latency for Denali Data Feed distribution. -LZ4 compression with compression performed on multiple threads. - Multiple data distribution threads, which have increased throughput of our real-time servers by at least three times and more depending upon the number of users. This was a recent improvement. There may be more things but this is all that comes to mind right now. 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: 2023-09-02 11:10:54
|