[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: eSignal bursting /SP #F/ES Question



PureBytes Links

Trading Reference Links

RE: SP eminis: Setup as an INDEX  (ES #F)  vs.  ES M5
If you setup ES/NQ's as index, and only use the #F (index) in your charting-
yet you still have the ES M5 set up as 'future' still in the GS, and still
collecting the data
(but NOT charting it) Would this still have a negative effect on your CPU?
Do you need to Delete altogether the ES H5 from the GS-
and ONLY collect the #F to make things run smoother, or is it only the
CHARTING
of the futures (ES H5) that affects things?

Best Wishes,
Marc Miller




----- Original Message ----- 
From: "etrader" <etrader@xxxxxxxxxx>
To: "'Dave Nadeau'" <davenadeau@xxxxxxx>
Cc: <omega-list@xxxxxxxxxx>
Sent: Friday, March 18, 2005 7:09 PM
Subject: RE: eSignal bursting


> Hi Dave,
>
> I also sent posted to esignal discussion forums
> and this was their partial response: " I haven't
> heard of any specific issues with TS2K, but I'll
> keep my eyes open for anything that resembles what
> you are experiencing and hopefully find a
> resolution"
>
> So if you come across any more posts from any
> other forums of other users of TS2k w/ esignal
> also experiecing this problem can you please pass
> the link to me.  I will collect them all and
> forward it to esignal.
>
> Thanks
> Bing
>
>
> >-----Original Message-----
> >From: Dave Nadeau [mailto:davenadeau@xxxxxxx]
> >Sent: Friday March 18, 2005 8:20 PM
> >To: etrader
> >Cc: omega-list@xxxxxxxxxx
> >Subject: eSignal bursting
> >
> >Hi etrader,
> >
> >e> If anyone using TS2ki with esignal IS, or IS
> NOT experiencing CPU
> >e> issues i would greatly appreciate their
> feedback just to give me
> >e> better indication whether this problem has
> more to do with
> >me than w/
> >e> esignal.
> >
> >
> >   I  for  one am experiencing the same thing. I
> saw a brief
> >   discussion  on  this  topic (and I posted) on
> the eSignal
> >   website, as well as several on EliteTrader.
> >
> >   I  know  that  this  isn't a GS/Omega problem
> because I'm
> >   using the same workspace that I've had with
> previous data
> >   providers.
> >
> >   I've done all the usual fixes: all futures are
> created as
> >   INDEX,  those  indicators that aren't required
> to are set
> >   not  to  update  every tick, my history that I
> collect is
> >   limited (as I am primarily scalping).
> >
> >--
> >Dave Nadeau
> >Fort Collins, CO
> >
>
>