Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Thu, 25 Apr 2024 18:07:31 +0000
[Locked] - Replay Chart DOM leads the chart
View Count: 3186
| [2018-12-10 19:12:44] |
| |
|
Now the 6 month estimation is very likely an overestimate. We just do not want to provide misleading information. We have no further advice other than what is documented in regards to your question above. The market depth data from CQG will always use the local timestamp. I have 'connect to market data server' set to TRUE. Do you recommend 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2018-12-10 19:12:53
|
| [2018-12-30 23:18:42] |
| User104854 - Posts: 441 |
|
Do you have any kind of an update on this?
|
| [2019-02-27 19:58:43] |
| User104854 - Posts: 441 |
|
Has there been any progress on this? One of the last responses was "there is not a millisecond level comparison with timestamps" but you were going to work on it. To re-iterate I'm looking for the DOM and chart to be in sync during replay so that I can fine tune my execution, automation, etc. I'm currently with CQG but I don't really care which data provider I use I just want it to work. I would use the Sierra Chart data feed but last I looked into this it wasn't working with your feed either. Hence the millisecond timestamp issue. Please advise. Thank you. |
| [2019-02-27 20:25:51] |
| |
|
We would still allow about another three months.
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 |
| [2019-03-07 22:51:22] |
| User104854 - Posts: 441 |
|
Great. Looking forward to it. The DOM and chart can be out of sync by as much as 2 seconds.
|
| [2019-03-07 23:16:29] |
| |
|
No, that cannot be possible. That would be due to a time stamping issue on your system and when using CQG. That is not a Sierra Chart issue. What we are referring to is a difference of more than one second. 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: 2019-03-08 03:34:06
|
| [2019-03-08 00:28:34] |
| User104854 - Posts: 441 |
|
It may be a CQG thing but I need Sierra Chart to tell me what the best solution is on how to fix it. Tell me how to best sync my computer so that it matches with CQG. It's extremely confusing. Do I set the local computer to TRUE or FALSE? Do I click on Set System Date-Time from Server? (which there is no option to tell if it's on or off. It's just on the dropdown.) If I use my local computer for the time then where do I sync it up with so that it matches CQG? I haven't seen any documentation anywhere on how to best solve this. It seems like it should be a simple fix so please direct me to where I can resolve it. |
| [2019-03-08 00:46:51] |
| User104854 - Posts: 441 |
|
On a side note I've spoken with CQG and they say that there's nothing wrong with their time stamping and to contact you regarding this.
|
| [2019-03-09 08:50:10] |
| |
|
The way to minimize the problem as much as possible at this time is to use the Sierra Chart Exchange Data Feed: Sierra Chart Exchange Data Feed That will minimize the issue to within less than a second. That is all we can say. We cannot help with CQG and we will not do 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2019-09-02 18:06:47] |
| User104854 - Posts: 441 |
|
So is this resolved now? I saw something about microsecond time stamps. The last post I got from you stated that by using the SC data feed that the DOM and chart will be within 1 second of each other on replay. Has this improved now? With CQG it's all but impossible for me to run an accurate backtest as I need the DOM and chart to actually be in sync and not lead and lag each other. If I switch to the SC data feed do I have to worry about my computer clock time stamp to make sure it matches with your data feed like I have to with CQG? I'm hoping not. Please advise. |
| [2019-09-03 02:45:02] |
| |
|
There is accurate millisecond time stamping for market depth data in the latest versions. So yes a significant improvement. Make sure you are running version 1983. We do recommend using this data feed though: Denali Exchange Data Feed If I switch to the SC data feed do I have to worry about my computer clock time stamp to make sure it matches with your data feed like I have to with CQG? No and this is no longer an issue with CQG either.
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: 2019-09-03 02:45:40
|
| [2019-09-03 12:42:24] |
| User104854 - Posts: 441 |
|
Ok. Thank you. So if this is no longer an issue with CQG then does it matter if I have 'timestamp using local computer clock' set to true or false? Is it better to set it to one or the other or does it matter? |
| [2019-09-03 14:36:22] |
| |
|
That setting is not used anymore.
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 |
| [2019-09-03 16:13:43] |
| User104854 - Posts: 441 |
|
I upgraded to 1983 but the software was using a lot more resources and was running very slow so I went with 1978. It says that the CQG time stamp changes were implemented on 1978 so this should work as well yes?
|
| [2019-09-03 19:31:40] |
| |
|
Should be definitely no difference between versions with performance. Makes no sense whatsoever there would be any difference unless the issue is specific to your system. Refer to help topic 30: High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often We do recommend using 1983. 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: 2019-09-03 19:31:55
|
| [2019-09-11 14:07:20] |
| User104854 - Posts: 441 |
|
I just upgraded to 1986 and there is a significant difference in performance compared to 1978. I've used them both this morning. I use a 1 tick range bar chart and with 1978 everything flows nicely and is very fluid. With 1986 it is choppy and lags. Every 3 seconds 3 or 4 bars print all at once. With 1978 everything is much faster. Also when I right click the chart and click on studies it takes 2 or 3 seconds to pull up the studies whereas with 1978 it is instant. Since 1978 works great and 1986 does not I can conclude that it has nothing to do with my computer or anything on my end. I've been using the same charts for a long time and they've never performed as bad as with this latest version so the only thing that makes sense is that 1986 has some changes that make it slower and less responsive. You must have made some sort of change that is causing it to use more resources or something and it's not performing as well. If I had the same issues with 1978 then I would guess that I need to address it on my end but like I said that version works great. Is this something you can look into and fix? |
| [2019-09-12 08:39:43] |
| |
|
Really we are not totally sure what the issue is but try version 1987. Refer to the notes for that here: https://www.sierrachart.com/index.php?page=doc/Whats_New.php#SCVer1987 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: 2019-09-12 08:41:02
|
| [2019-09-12 17:13:59] |
| User104854 - Posts: 441 |
|
I understand. I tried 1987 and it's still incredibly choppy and a lot of lag. I do have quite a few studies on this chart and a handful of overlays but it doesn't seem to affect things with version 1978. I guess I'll stick to that for now and hopefully it'll work it's way out in future versions.
|
| [2019-09-12 22:10:59] |
| |
|
In your case we do not know what the problem is. We can only refer you to help topic 30: High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often 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: 2019-09-12 22:11:14
|
To post a message in this thread, you need to log in with your Sierra Chart account: