|
PureBytes Links
Trading Reference Links
|
Hi Dennis,
Yes, it's set up as Index.
My post says that this problem just started
occuring about 3 wks ago coinciding with esignals
mention of "CME Bursting Data".. maybe it should
be more accurately called "esignal Bursting data"
If it was setup as Futures, i would have had
experienced this problem long ago
Cheers,
Bing
>-----Original Message-----
>From: DH [mailto:catapult@xxxxxxxxxxxxxxxxxx]
>Sent: Friday March 18, 2005 7:37 PM
>To: Omega List
>Subject: Re: (etrader)
>
>> Running TS2K during this time caused the cpu to
spike and
>stay at 100%
>> for much longer than usual periods even during
a low volume turnover
>> rate (ie <3000 contracts/min).
>
>That's pretty big volume for the CME. Do you have
the minis
>set up as indexes? TS2K has a "volume bug" if you
set them up
>as futures and you can see CPU overloading such
as you
>describe. Make sure you tell it to ignore the
bid/ask ticks as
>there are many more of those than real trades.
>
>--
> Dennis
>
|