Login Page - Create Account

Support Board


Date/Time: Sat, 18 Jan 2025 19:43:49 +0000



replay issue

View Count: 652

[2018-02-23 22:44:03]
User98657 - Posts: 329
I've been using replay all day, and it's been fine. a little slower than i might have expected, but not terrible.

All of a sudden, it seems to have ground to a halt. even at 1x using Standard Replay, i'm getting a buffering wheel on my screen waiting for new bars to appear.

I'm replaying one day of the NQ (2/20/2018) on a 4-tick renko chart, using tick data. Like I said, it's been fine all day and now it just won't seem to function.

i've done a complete shut down and restart, updated to the most current version, closed all other programs and still nothing. (I mean it is running, but really, dragging)

I have a newer generation I7 machine with 16GB of memory and very good video processor. I'm not having issues with other programs such as excel. my cpu usage as i write this and try to replay is roughly 4% - 6%, memory is at 31%.

Any suggestions????
[2018-02-23 22:56:57]
Sierra Chart Engineering - Posts: 104368
So is Sierra Chart in a completely frozen state when this is happening?

Before you start the replay, remove the studies (Analysis >> Studies) from the chart to see if it is possibly a study causing this issue.
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
[2018-02-24 01:28:19]
User98657 - Posts: 329
Thank you, i have it, and have to apologize.

i was working with the spreadsheet for the chart and added a few rows.
i increased the row count from 1000, to 3000. normally i wouldn't have thought too much of it, but i figured out that's what was slowing it down.

i have several columns of index/nmatch along with some other stuff and i guess all those calcs for every bar was just crushing the cpu thread.

Thanks for reaching out.

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account