Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Fri, 03 May 2024 13:25:10 +0000
Post From: Allow Disabling of Compression or Do It in Another Thread
| [2013-11-18 06:30:30] |
| |
|
The only issue I saw was that SC writes each record one by one (40 bytes each) which has a huge overhead of constantly calling into WriteFile(). If this were really true, this would have been resolved 15 years ago. This is not correct. This is a very efficient function and the OS does very good caching. You can actually see, that there have been more than 6 million records written in a reasonable amount of time. The problem is at the very end with the final data copy.This is the source of the problem: HD Request # 3 - Copying downloaded Intraday chart data from @CD#.temp.scid to @CD#.scid | 2013-11-17 23:18:53 Update to the latest prerelease, this is more efficient now. Compressing file: M:\SierraChart\Data\@CD#.scid. This may take a while... | 2013-11-17 23:18:53 HD Request # 3 - Timestamp of first Intraday data file record written: 2006-04-21 03:35:00 | 2013-11-17 23:18:53 HD Request # 3 - Intraday download COMPLETE for @CD# | 2013-11-17 23:21:02 If you still have a problem there is going to be an issue with the file system on your side. This process only takes us a couple of seconds, even with older versions, where as on your side it is taking about two minutes. This is not normal. Even with the way it was designed. Nevertheless, we are going to write data in batches during a historical data download. I will try to get that out by tomorrow. We do agree that historical data downloading should be on a background thread. It is done that way for most services that Sierra Chart supports. It is not done this way for IQ Feed but will be once IQ Feed is moved into a separate process through a DTC Bridge program. This is something we will be doing next year. . I hate when the GUI's of programs become unresponsive because they have a task that should be in the background in the foreground. Yes. We agree, but this is not a normal case. The main problem you are having appears to be a system problem on your side. However, the latest prerelease should make a significant difference. Try again.And this is also why we have developed the DTC protocol and an overall Data / Trading service integration architecture by using separate process servers to take the load of interfacing with those services into another isolated process and thread. 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: 2013-11-18 06:35:41
|