TJ, Sorry. I should have mentioned, I have n=1 and 'n last quotations' selected.
TIA --- In [email protected], "Tomasz Janeczko" <gro...@...> wrote: > > Hello, > > PRECISION. That is a key word. Follow precisely what I write. > > I wrote something different: > > Buy = 0; > > *NOT* 1 > > It makes huge difference because with 100000 bars, buy = 1 means > OUTPUTTING 100000 lines of texts per symbol, so in your case it will be > outputing > 2.4 million lines of texts. Not something that can be done in few seconds. > > Best regards, > Tomasz Janeczko > amibroker.com > ----- Original Message ----- > From: "sidhartha70" <sidharth...@...> > To: <[email protected]> > Sent: Wednesday, September 02, 2009 12:37 AM > Subject: [amibroker] Re: Scan times > > > > TJ, > > > > Just to illustrate the 'black magic element' of all this... I just set up > > one line of code as you suggested, > > > > Buy = 1; > > > > I've now run a few scans across my filter watchlist using that code. > > > > So far I've seen variations in scan time from 22 seconds to almost 4 > > mins... that's using an IQ Feed DB. > > > > Is this kind of behavior normal...? > > > > > > --- In [email protected], "Tomasz Janeczko" <groups@> wrote: > >> > >> You don't provide any formula or any details to help you, > >> but you should try > >> > >> Buy = 0; Sell = 0; > >> > >> scan. It will show you "data access" only speed. It is *BASE* time > >> below which you can go down because the data source is limiting you. > >> > >> On my eSignal intraday database that has 200000+ bars per symbol > >> scanning 124 symbols with such basic formula takes 6 seconds > >> (all symbols streaming and backfilled already) > >> > >> Any time above that base time is caused by the formula you wrote. > >> > >> Best regards, > >> Tomasz Janeczko > >> amibroker.com > >> ----- Original Message ----- > >> From: "sidhartha70" <sidhartha70@> > >> To: <[email protected]> > >> Sent: Tuesday, September 01, 2009 11:39 PM > >> Subject: [amibroker] Re: Scan times > >> > >> > >> > TJ, > >> > > >> > doesn't seem to help... I'm running it now with 'wait for backfill' > >> > unchecked. Same huge wait time. > >> > > >> > Scan's are like black magic I find... the time they take seems to bear > >> > no resemblance to the code behind them... worse than > >> > that, > >> > I have seen huge variations in the time taken to run exactly the same > >> > scan across the same number of bars & same symbol list. > >> > > >> > Often they seem to jam up or have a 'mini hang'. > >> > > >> > I'm at a loss. Any ideas...? 14 mins can't be right. Anything more than > >> > a couple of mins can't be right surely...? Even that > >> > sounds a lot. > >> > > >> > --- In [email protected], "Tomasz Janeczko" <groups@> wrote: > >> >> > >> >> Uncheck "wait for backfill". > >> >> > >> >> Best regards, > >> >> Tomasz Janeczko > >> >> amibroker.com > >> >> ----- Original Message ----- > >> >> From: "sidhartha70" <sidhartha70@> > >> >> To: <[email protected]> > >> >> Sent: Tuesday, September 01, 2009 9:54 PM > >> >> Subject: [amibroker] Scan times > >> >> > >> >> > >> >> > I'm confused. > >> >> > I have a scan that I call every 5 mins (or hope to). This scan is > >> >> > used to set up a series of static arrays that I use > >> >> > elsewhere > >> >> > in > >> >> > my code. > >> >> > > >> >> > The scan code is 30 lines long. A 'check' of the code says it takes > >> >> > 0.035 secs to run. > >> >> > > >> >> > I'm running the code over a defined filter which is a watch list of > >> >> > symbols. It runs across 24 symbols. > >> >> > > >> >> > My DB has 100,000 bars in it. > >> >> > > >> >> > Even with everything backfilled, I have seen this scan take 14 mins > >> >> > to run. That can't be right can it...?? > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > ------------------------------------ > >> >> > > >> >> > **** IMPORTANT PLEASE READ **** > >> >> > This group is for the discussion between users only. > >> >> > This is *NOT* technical support channel. > >> >> > > >> >> > TO GET TECHNICAL SUPPORT send an e-mail directly to > >> >> > SUPPORT {at} amibroker.com > >> >> > > >> >> > TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at > >> >> > http://www.amibroker.com/feedback/ > >> >> > (submissions sent via other channels won't be considered) > >> >> > > >> >> > For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG: > >> >> > http://www.amibroker.com/devlog/ > >> >> > > >> >> > Yahoo! Groups Links > >> >> > > >> >> > > >> >> > > >> >> > >> > > >> > > >> > > >> > > >> > ------------------------------------ > >> > > >> > **** IMPORTANT PLEASE READ **** > >> > This group is for the discussion between users only. > >> > This is *NOT* technical support channel. > >> > > >> > TO GET TECHNICAL SUPPORT send an e-mail directly to > >> > SUPPORT {at} amibroker.com > >> > > >> > TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at > >> > http://www.amibroker.com/feedback/ > >> > (submissions sent via other channels won't be considered) > >> > > >> > For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG: > >> > http://www.amibroker.com/devlog/ > >> > > >> > Yahoo! Groups Links > >> > > >> > > >> > > >> > > > > > > > > > > ------------------------------------ > > > > **** IMPORTANT PLEASE READ **** > > This group is for the discussion between users only. > > This is *NOT* technical support channel. > > > > TO GET TECHNICAL SUPPORT send an e-mail directly to > > SUPPORT {at} amibroker.com > > > > TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at > > http://www.amibroker.com/feedback/ > > (submissions sent via other channels won't be considered) > > > > For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG: > > http://www.amibroker.com/devlog/ > > > > Yahoo! Groups Links > > > > > > >
