You don't say, but it appears that this is running on real time data. Anyway, here are some things that I've used to speed up my real time scans. I run a scan every 1 minute over 150 symbols - it takes about 3 seconds to complete. To get there I used Task Manager -> Performance -> Resource Monitor to check for bottle necks.
Here is what I did to speed things up. 1. my database is small - 2500 bars of 5 minutes each for about 150 symbols. (Only the "Hard Right Edge" is important for me.) I have another larger db that I use for historical testing. What happens is when each new bar arrives, the oldest bar gets deleted and the run times remain constant. 2. Make sure that all unnecessary programs are not running. The biggest offender for me was a real time virus checker "Windows Defender". Run Task Manager - Processes when your scan is running to see if other programs are competing for CPU time. For me Broker.exe uses about 20% of CPU #2 and IQConnect.exe uses about 5-10% of CPU #1 3. Make sure you have plenty of memory. Zero page file usage. 4. Eliminate the window pane effect around the edge of each window you have open - I forget how to turn that off. 5. Make sure that your cpus are not running in "power save" mode. 6. Look through your *.afl and eliminate all unnecessary code. I had several lines that I used for debugging laying around. --- In [email protected], "sidhartha70" <sidharth...@...> wrote: > > 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...?? >
