|
PureBytes Links
Trading Reference Links
|
Bilo,
How about the Commentary in systems. Expert Commentary. Is this a
factor?
One thing that happens every so often to me is a workspace becomes
partially corrupt and hogs CPU. I don't know what causes it but my
workaround is this. My main workspace is called Bigspace. When I
built it I then saved it as Bigspace2, Bigspace3... up to about 5 of
them. If I have a problem I shut charting down and open MyWork and
rename Bigspace to BigspaceC or just delete it. Then I rename
Bigspace2 to Bigspace and open charting.
Needless to say NEVER RUN TRACKING CENTER. This is a really fat hog.
Jimmy Snowden
Friday, April 25, 2003, 9:48:10 AM, you wrote:
Bilo> i had similar problem with TS 6.0 hogging up cpu, "in fast markets" with plenty of ram and cpu power
Bilo> the culprit was that forgot to remove debug print statements from EL studies that were sending
Bilo> data to TS print log. when i commented those out i no longer had any problems even with UET enabled
Bilo> on very complex EL studies...even in the fastest of the markets... and just to make sure i tested
Bilo> it on W98 350Mhz/128M very old machine... no problem there either... in fast markets...
Bilo> the configuration was 8 SP charts one workspace about 2500 bars in each chart, Update Every Tick enabled
Bilo> on all studies, 3 studies per chart, 1 very complex, ie pretty good load for TS :-)
Bilo> bottom line: EL print statements will kill your CPU... comment those out when trading real time...
Bilo> bilo.
Bilo> ps. i was sending about 5 vars to printlog on every bar from every chart... printlog window was not open.
|