I have been looking around for a while to solve the "cron stuck" matters of Aggregation or FeedAPI.

First I understood that matter is the PHP's execution time. Most shared hosts have this value set to 30 secs. If you have lots of feeds, this is causing some feeds not to update or getting cron stuck.

what I did is to get a VPS, to be able to change php.ini's max. PHP execution time. I changed the value from 30 to 480. Now cron runs every hour and updates around 60 feeds without any matter. Cron can update all feeds and never got stuck so far.

a feed takes app. 4 secs. to be updated. so if you have 100 feeds, you should set PHP execution time to 480 for ex. and it's ok afterwards.

there are also shared hosts out there that allow php.ini modification but in this case your host might be claiming on high server resources usage for a few minutes.

hope this helps to everyone.

Comments

alex_b’s picture

alex_b commented
Status: Active » Closed (fixed)

drupallogic: while this is great advice, unfortunately I'll have to close this issue, because the queue focuses on FeedAPI build tasks only. For efficiency's sake I'm trying to keep issues only if they are actionable (right away or in the foreseeable future) for work that will go into FeedAPI.

You could post this on the rss-aggregation group on groups.drupal.org .

Thanks!