Support Board
Date/Time: Wed, 14 May 2025 07:50:34 +0000
Post From: SC burns CPU resources on continually accessing data files even with markets closed
| [2016-04-26 02:59:52] |
| |
|
Did you not read the part that said "but this may be a non-issue and just part of the access function" ?? It's possible for a statement to be made and then a counter-balancing statement to also be attached to that sentence. Example: "it looks like this, but there's a chance it could actually be this." Monitoring/tracing of a process has zero relation to the CPU usage of it.
Obviously in this case it does. And certainly the process of debugging/monitoring does introduce additional processing. We have plenty of experience with that.It is pointless to go through an elaborate effort to avoid periodically checking files that are currently open when there is a non-issue here. If we hear from other users, about a problem related to this and that is definitively confirmed, then we will look at it. But look at our prior posting with the extreme test we performed and no impact. And we do appreciate the interest in trying to make Sierra Chart better, but we do not think this is approached properly. This thread is now locked. It is unnecessarily taking our time. 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: 2016-04-26 04:50:35
|