[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [amibroker] Re: Best practices on tuning up Amibroker for faster scanning



PureBytes Links

Trading Reference Links

I am using esignal RT feed and I scan about 18 forex pairs and I have about 12 strategies running in the AFL. No loops. But lot of multitimeframe coding.
 
I am going to upgrade from 768mb to 2GB mem and see if it makes any differennce.
 
I wish there was like a progress bar showing which line of code is being executed while elasped time is displayed, so that I can see which module of code is slowing things relatively speaking.
 
Worstcase I may have to bump up the scanning interval to 2min. One option I think that would be helpful is to enable scan at the completion of the bar per periodicity set. Say periodicity is set to hourly, as soon as the hourly bar is
complete, initiate a scan.
 
 
Cheers,Padhu
 
 
 
----- Original Message -----
Sent: Friday, September 21, 2007 2:46 PM
Subject: [amibroker] Re: Best practices on tuning up Amibroker for faster scanning

What is ur datasource. I find DTNIQ to be causing heavy cpu cycles.
the same scans that i was running last week is now slowing my system.
if i shut down the connector and run it connected to a different
datasource like IB, it is normal.
If anyother are having same issues with DTNIQ, i would appreciate
response because i am going to complain to them now.

For the last 2 days, it is so bad that i cannot use the DTN data
source at all. Maybe the 75 dollar savings compared to esignal is not
worth it.

In terms AB optimizations,
1. i run 2 scans, i run a EOD scan to filter out potential candidates
adn put them in a watchlist. then i run a realtime scan on the
watchlist to get me my results. obviously, loops would add to the
execution times.
2. i have noticed that repeat scans on the same formula returns data
quicker. i guess, the first time, it has to backfill lot more. so i
start running my realtime scans before 9:15 am so that by the time
the market opens, the scans are runnign faster.
Finally, this week DTNIQ is a resource hog. really big time.
--- In amibroker@xxxxxxxxxps.com, "Padhu" <ccie8340@xx.> wrote:
>
> Hello,
>
> I am running Amibroker ver 4.9 on Dell single 2GHZ CPU with 768mb
ram.
> Just checking to see if anyone can share some
> Best practices on tuning up Amibroker for faster scanning.
>
>
>
> 1. What are the things that can be be done on the system to improve
scanning time?. My scan interval is set for a min, but sometimes
elapsed time is about 90 seconds.
>
> 2. Any recommendations on CPU/Mem usage?.
>
> 3. Anything in AFL that is known to be a resource hog and should
not be used or coded better shall we say?.
>
> 4. If scanning is done every min, do I still need backfill?. Isn't
backfill required only when previous bars data is missing in the
database?.
>
>
>
> Thanks.
>
>
>
> Cheers,Padhu
>

__._,_.___

Please note that this group is for discussion between users only.

To get support from AmiBroker please send an e-mail directly to
SUPPORT {at} amibroker.com

For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG:
http://www.amibroker.com/devlog/

For other support material please check also:
http://www.amibroker.com/support.html




Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe

__,_._,___