So it's AFL specific...?? And given that code is always changing/evolving it's a moving target...?
Ummm. That makes things trickier. I guess I'll just have to experiment. --- In [email protected], "paultsho" <paul.t...@...> wrote: > > That depends on how many arrays you use in your afl. > for example, if each field on a record is loaded, it uses up 40 bytes > but each array is only 4 bytes * nSize. 1 M of L2 cache will keep 250 bars of > a single array, ie 25000 bars will need 10 M of cache. There are roughly 400 > bars of 1 min per day session or 2000 bar per week. > > --- In [email protected], "sidhartha70" <sidhartha70@> wrote: > > > > Brilliant TJ. Thanks. > > > > Question... I want to start looking at some n-sec timeframes. > > > > Mainly 15 sec, and 30 sec. > > I currently use a 25,000 bar 1 min DB which runs super quick because it > > keeps all the data within the CPU cache, and also gives me about a weeks > > work of data on the e-mini's which is all I need for day trading. > > > > To get 15 sec & 30 sec intervals, I assume I am best to set my DB base > > interval to 15 sec, and then set a 30 sec interval up via > > preferences>intraday....?? > > > > Any ideas how far I can push the number of bars to in my DB and keep all > > the data in CPU cache still to keep the speed high...?? > > > > I'm running an Intel Xeon X5365 CPU. > > > > TIA > > > > --- In [email protected], "Tomasz Janeczko" <groups@> wrote: > > > > > > Hello, > > > AmiBroker 5.28.0 BETA released: > > > > > > http://www.amibroker.com/devlog/2009/08/22/amibroker-5-28-0-beta-released/ > > > > > > > > > Best regards, > > > Tomasz Janeczko > > > amibroker.com > > > > > >
