|
PureBytes Links
Trading Reference Links
|
Hi Marc,
mm> RE: SP eminis: Setup as an INDEX (ES #F) vs. ES M5
mm> If you setup ES/NQ's as index, and only use the #F (index) in your charting-
mm> yet you still have the ES M5 set up as 'future'
mm> still in the GS, and still
mm> collecting the data
mm> (but NOT charting it) Would this still have a
mm> negative effect on your CPU?
mm> Do you need to Delete altogether the ES H5 from the GS-
mm> and ONLY collect the #F to make things run
mm> smoother, or is it only the
mm> CHARTING
mm> of the futures (ES H5) that affects things?
My understanding is that the problem occurs in the GS. To
be certain, I've always set up both forms of futures
contracts, my ES #F, ES M5, NQ #F,...etc. as INDEX. When
we roll over, I just rename them in the Global Server and
the eSignal Data Manager.
I know my last statement begs a question, so in case you
are wondering, the data bursting and CPU saturation was
occurring before the contract roll. I started eSignal in
mid-Jan, so I had only a partial contract's worth of data
in my GS.
Regarding your question on pagefiles, I've got my system
forced to a 2G pagefile size.
--
Dave Nadeau
Fort Collins, CO
|