The support forum is built with (1) General and FAQ forums for common trading queries received from aspiring and experienced traders, and (2) forums for course video topics. How to Trade Price Action and How to Trade Forex Price Action videos are consolidated into common forums.
Brooks Trading Course social media communities
Multiple Issues with TS Freezing
Greetings all -
During ~8 months of Tradestation usage, I've experienced multiple instances of platform freeze. When this occurs, I'm totally locked out of the platform. In most cases, restarting the software, or restarting my PC in addition to the software, is not a resolution.
This issue has sometimes correlated to obvious high volume / high volatility, such as an FOMC announcement, but not always.
On the most recent call with TS support, I was told that this, along with server disconnects, is the number one issue they deal with. I'm curious to know if others have encountered this problem?
During that call, I was shown how to watch the platform's CPU draw, and determined it was overloading my 6-core CPU. I've run multiple different trading software on this machine, some of which is CPU-intensive (such as IBKR's TWS), and have not had any issue. Also worth noting that this PC is dedicated to trading - I run nothing else on it.
Nonetheless, I thereafter upgraded to a 24-core CPU; this PC is now quite the beast. After the upgrade, I ran benchmarking on the CPU and it performed flawlessly.
However, this issue persists, hence I'm reluctantly approaching a switch away from TS. I'm hoping to avoid this, as issues aside, I really like it.
Another possible correlation I've made regarding this issue is with the candle timer. I'm using a script found on the forum called 'Time Remaining in Bar'. Is this what others use?
I ask because I've found multiple versions of other custom studies on the forum, and if alternative versions of the timer exist, this might be something I can test. I'm running TS10 with the most recent update (68) installed.
Thanks for any input on this really problematic issue.
I feel stand-alone desktop applications have had their day. Whether it's TS, eSignal,... all suffer lags during high volatility. With applications constantly getting heavier, you have to keep upgrading your hardware all the time just to keep up.
I think browser-based lightweight software like TradingView are the future.
Thanks for jumping in. I don't disagree. However, this post has been created because I need a solution for an issue I am experiencing in the here and now. With respect, I do not want it hijacked with opinions about how things should be.
Thought I'd provide the solution found to issues stated above. It was quite simple, in fact.
Under File > Preferences > Network > Streaming Data Optimization, I moved the slider to high. Have not had a single issue since.
Could it be your internet connection? Also had some issues with my platform lagging. For me the cursor would move very slowly. Also at one point the chart stopped updating. I called TS and walked me through deleting the cashe (sp?) folder for TS. That worked for me for a couple of days. It ultimately the issue came back. I deleted the software and reinstalled it again. I don't seem to have any issues so far. (knocking on wood!)
My ISP service is for ~100MPS, and that's typically what I get when running speed tests. My PC has direct ethernet connection to the router.
I've walked through that cache deletion step with TS support at least half a dozen times, along with deleting and reinstalling the application, and then installing a new instance of TS into an entirely new user profile. None of these fixes provided a solution.
I am surprised their support never suggested the Network setting, which has provided a fix.
Zero lag throughout FOMC today, which is a first since I begin using TS.
Have you run TS without the 'Time Remaining in Bar' script?
I do, along with the bar counting script.
Prior to the setting change described above, TS would often provide an error related to the computer clock. I figured it was due to the time remaining script.
Anyway, zero issues since changing that setting.