Closed MicroTrendsTom closed 3 years ago
jmscraig
commented
3 years ago I noticed neither Q related bool is enabled.
Will you be testing with no Q enabled?, default Q?, a variety of Q state tests?
FYI.. in todays test both Reverse clients are still rocking (1 sec, 2 sec) While both MACross sample strategy clients have hung / frozen the charts running them.
jmscraig
commented
3 years ago Somewhere Tom posted ~~"that he felt possibly that running strategies headless (without a chart) is more reliable because of client workload pressures and complexities. " .. or something like that
Beyond that Strategy instantiation or restart can sometimes be different between running from a chart and not, I am guessing this a least sometimes has something to do with what we include in OSC() and what OSC() state we land it in.
This surfaces the question "Could OSC() configuration design be a contributor to occasional reliability concerns?"
Just brain storming.
MicroTrendsTom
commented
3 years ago Results all good - no lock up on 1 Second Reversal strategy
VS 2019 debug break start/pause no locks
Chart no deadlocks - NT8 no Deadlocks
Trace file no locks or or unhandled exceptions
No exception on disconnect
Can reconnect and continue if desired
MicroTrendsTom
commented
3 years ago I noticed neither Q related bool is enabled. Will you be testing with no Q enabled?, default Q?, a variety of Q state tests?
This would need to be tested but today i have to use the current version of the Engine and finish off a project using it and so testing the Q wont be on the agenda - as yet etc but for sure it needs to be done
reversal 1 Second Chart Debug open in VS Studio Detailed Tracing
Will turn this on for about 8 hours then a scheduled connect to the same datafeed will stop the strategy and we will also look for issues on that event