|
PureBytes Links
Trading Reference Links
|
I agree, it seems like a trivial amount of memory per stock, but we should
be careful not to also trivialize the amount of memory potentially consumed
for "real" use of MetaStock.
I'd assume that with multiple stocks, multiple indicators (they use memory
too), explorations, experts, system tests with many optimizations, test
across multiple stocks (if ever offered), etc., it could all add up quickly.
My vote is of course for double precision ASAP, so I can stop relying on
Excel as much and use MetaStock as I originally intended. But, IMO as a
programmer, this doesn't seem like a minor internal patch to the product.
Wayne
> -----Original Message-----
> From: owner-metastock@xxxxxxxxxxxxx
> [mailto:owner-metastock@xxxxxxxxxxxxx]On Behalf Of Allan Havemose
> Sent: Friday, 4 May 2001 8:45 AM
> To: metastock@xxxxxxxxxxxxx
> Subject: RE: Current Day!
>
>
> Ups ... my fingers got ahead of my brain :)
>
> There memory consumption difference is probably about 700k, due to
> open, high, low, close, volume, oi and date/time.
>
> Argument still valid, though.
>
> Allan
> --- Allan Havemose <havemose@xxxxxxxxx> wrote:
> > The memory argument is getting a bit dated:
> >
> > If you have 50000 bars for a security and load it all, it requires
> > 100k
> > with single precision and 200k with double precision.
> >
> > I'd trade precision for 100kb of RAM anytime! Even with 10 charts
> > open,
> > we're only talking about 1 MB.
> >
> > Secondly, floating point calculations are generally faster in double
> > precision than single precision.
> >
> > Allan
<snip>
|