|
PureBytes Links
Trading Reference Links
|
Thanks to all who replied here and privately.
You may do me a favor another way - just by subscribing to Dynastore for
eSignal :))))
Throw away this 2000i with all its bugs and enjoy TS4 with eSignal in
realtime....
DB
----- Original Message -----
From: "Bill Wynne" <tradewynne@xxxxxxxxxxx>
To: <dynastore@xxxxxxxxxxxx>; <omega-list@xxxxxxxxxx>
Sent: Friday, August 17, 2001 1:48 PM
Subject: Re: TS2000i bogged down
> Ooops :-/
>
> .... too many years on Maui: that would be he
> mo' betta' understands TS or he understands TS better....
> AND he speaks English better than me LOL.
>
> BW
>
>
> >From: "Bill Wynne" <tradewynne@xxxxxxxxxxx>
> >To: dynastore@xxxxxxxxxxxx, omega-list@xxxxxxxxxx
> >Subject: Re: TS2000i bogged down
> >Date: Fri, 17 Aug 2001 10:27:13 -0700
> >
> >Ya gotta love DB:
> >
> >He better understands TS better than Omega, Signal better than
> >DBCC, and QCharts/QFeed better than TRLY.... and he often offers
> >better support than all three from the outside looking in. <VBG>
> >
> >Thanks DB,
> >
> >BW
> >
> >
> >>From: "DB" <dynastore@xxxxxxxxxxxx>
> >>To: <omega-list@xxxxxxxxxx>
> >>Subject: Re: TS2000i bogged down
> >>Date: Fri, 17 Aug 2001 12:56:58 -0400
> >>
> >>There is nothing to do with Windows 2000 - it's the same at Win 95, 98,
> >>Me,
> >>NT and 2000.
> >>
> >>The bug is in "DBC Subserver" and "DBC Online Subserver" of Global
Server
> >>and it's very simple: if the trade quote for the Futures symbol has
> >>TradeVolume different from zero, it causes Global Server to get all
> >>available CPU resources for some amount of time and this causes chart
> >>flicks, hour glass mouse cursor etc.
> >>Ex-Omega just hard-coded the old behavior of DBC Signal data feed - no
> >>trade
> >>volume for the Futures.
> >>
> >>This is not the issue for any other kind of symbols, so you may add your
> >>"ES
> >>U1" to Global Server as STOCK (with the same settings - CME as the
> >>exchange,
> >>price scale, exchange settings etc) - and it will work correctly.
> >>
> >>
> >>DB
> >>
> >>----- Original Message -----
> >>From: "dhdavis" <dhdavis1@xxxxxxxx>
> >>To: "Bob Claycomb" <claycomb@xxxxxxxxxxxxxx>; <omega-list@xxxxxxxxxx>
> >>Sent: Friday, August 17, 2001 12:46 PM
> >>Subject: Re: TS2000i bogged down
> >>
> >>
> >> > Hello John,
> >> > I am using TS2000i and eSignal and I am not having your problem. I
use
> >>a
> >> > disk cache program(O&O 2000) so that might help. I also use Win2000
and
> >>that
> >> > might make a difference, I don't know what OS you are using. I
switched
> >>to
> >> > Win2000 the first of the year and it was one of the best moves I have
> >>made.
> >> >
> >> > Dana
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > ----- Original Message -----
> >> > From: "Bob Claycomb" <claycomb@xxxxxxxxxxxxxx>
> >> > To: <omega-list@xxxxxxxxxx>
> >> > Sent: Friday, August 17, 2001 11:47 AM
> >> > Subject: RE: TS2000i bogged down
> >> >
> >> >
> >> > > You didn't mention which data feed you are using, or when you
started
> >> > having
> >> > > problems, but the description matches a TS2000i issue which started
> >>on
> >> > > August 16th for those using eSignal. On that date eSignal updated
> >>it's
> >> > data
> >> > > feed to include volume data on the e-mini contracts. For some
> >>reason,
> >> > > TS2000i processes this additional data very inefficiently, forcing
> >>cpu
> >> > > utilization to 100 percent. CPU utilization is driven to 100
> >>percent,
> >> > even
> >> > > if collecting data on only one e-mini contract. Of course, this
> >>slows
> >> > > everything else on the system to a crawl.
> >> > >
> >> > > I spoke to Omega on the phone yesterday, and they are aware of the
> >> > problem,
> >> > > but have no estimated date for resolution. They claim to have had
no
> >> > > knowledge of this major bug prior to yesterday, but that is not
true.
> >> > This
> >> > > same issue came up around two years ago with the QFeed/DynaStore
data
> >>feed
> >> > > combination. Omega failed to fix the problem then, and Dynastore
> >> > responded
> >> > > by enhancing it's product to include an option for stripping the
> >>volume
> >> > data
> >> > > from QFeed before feeding it to the GlobalServer.
> >> > >
> >> > > My concern is that Omega will be very slow in offering a fix in an
> >>attempt
> >> > > to force eSignal data users to migrate to the new TS platform. As
an
> >> > > alternative fix, eSignal could modify their feed or software to
> >>exclude
> >> > the
> >> > > e-mini volume information for those customers using TS2000i.
> >> > >
> >> > > Bob Claycomb
> >> > >
> >> > > -----Original Message-----
> >> > > From: John L. Perko [mailto:Kingbassbone@xxxxxxxxxxxxx]
> >> > > Sent: Friday, August 17, 2001 8:39 AM
> >> > > To: omega-list@xxxxxxxxxx
> >> > > Subject: TS2000i bogged down
> >> > >
> >> > >
> >> > > Hello omega list,
> >> > >
> >> > > Does anyone have a clue as to what would cause my intraday charts
to
> >>act
> >> > as
> >> > > if it is running in mud? After every few ticks received on a chart,
> >>the
> >> > > hourglass pops up for a second. Also, it takes a bit longer to
change
> >> > pages
> >> > > than before...as well as scrolling back on a chart. I also keep
> >>getting
> >>a
> >> > > message "Waiting on Server Data" when scrolling back.
> >> > >
> >> > > I did a complete reinstall of 2000i as well as a Defrag but it
> >>hasn't
> >> > > improved anything. If anyone has any clues, I would greatly
> >>appreciate
> >>it.
> >> > >
> >> > > Thanks,
> >> > >
> >> > > John Perko
> >> > >
> >> > >
> >> >
> >> >
> >>
> >
> >
>
>
|