There are High CPU Load Messages being issued on our VPN Server, whenever a trade is triggered and executed. There are four simultaneous workspaces running. There are eight separate datasets (two datasets per workspace) being read and processed by the workspaces. This High CPU Load issue obviously does not seem to be data oriented. The CPU utilization is very low between the times orders are executed.
Screenshot attached.
I have set up all of MC's recommendations, do not view Trade Bar, do not view Order and Position Tracker Window, Ignore Tick Cache in Realtime, etc. Those things do not seems to influence or reduce the issuance of the High CPU Load issues.
Anyone experiencing similar High CPU Load messages? Any recommendations regarding the elimination of the High CPU Load messages?
Thanks!
High CPU Load Messages
-
Kate MultiCharts
- Posts: 596
- Joined: 21 Oct 2020
- Has thanked: 9 times
- Been thanked: 148 times
Re: High CPU Load Messages
Hello eegroup,
The message is a part of the Fail-Watch system. It was designed to warn customers about possible issues.
Mostly, these messages are purely recommendatory, so if you are satisfied with the current performance, do not observe any issues in the operation and consider them excessive, you can change the timeout or completely disable them in MultiCharts -> File -> Preferences -> Trading tab -> Fail-Watch and trading system warnings.
Most likely, a slight spike in your CPU usage occurs, and as you have the timeout set too tight, the alert gets triggered. Increasing the timeout should help you in this case.
The message is a part of the Fail-Watch system. It was designed to warn customers about possible issues.
Mostly, these messages are purely recommendatory, so if you are satisfied with the current performance, do not observe any issues in the operation and consider them excessive, you can change the timeout or completely disable them in MultiCharts -> File -> Preferences -> Trading tab -> Fail-Watch and trading system warnings.
Most likely, a slight spike in your CPU usage occurs, and as you have the timeout set too tight, the alert gets triggered. Increasing the timeout should help you in this case.