[drupal-devel] [feature] Pass include and exclude parameters to cron.php for fine grained cron timing

Wed Jul 27 16:18:28 UTC 2005

Issue status update for 
http://drupal.org/node/19173
Post a follow up: 
http://drupal.org/project/comments/add/19173

 Project:      Drupal
 Version:      cvs
 Component:    base system
 Category:     feature requests
 Priority:     normal
 Assigned to:  robertDouglass
 Reported by:  robertDouglass
 Updated by:   Bèr Kessels
 Status:       patch

-1 on this one.
I think the hook_cron should carry the logic whether or not it wants to
be ran. Maybe aintroduce an API that allows theis checkto be done
easier? drupal_elapsed_run($name, interval)  that will check when $name
was last updated, if it was longer then $interval ago, return TRUE, and
update the last run of $name.

Bèr Kessels

Previous comments:
------------------------------------------------------------------------

Sun, 20 Mar 2005 10:08:59 +0000 : robertDouglass

Attachment: http://drupal.org/files/issues/cronpatch.txt (1.99 KB)

Some sites need fine grained timing for cron runs. For example, a site
that relies heavily on moblogging, mailhandler or any other email based
function would want to connect with the email server pretty often, say
ever 2-5 minutes. On another site I'm working on we generate flat files
for all of a certain node type on a regular basis, though not every 2-5
minutes. Thus the need for cron tasks on different schedules. This
patch allows you to make a list of modules to either include or exclude
when running cron, so that several cron tasks for one site can be
defined. The default behavior in the absence of both parameters is to
run all, so the patch preserves backwards compatibility.

 * Examples:
 *
 * runs all hooks
 * http://mysite.com/cron.php
 *
 * runs all hooks except the search and aggregator modules
 * http://mysite.com/cron.php?exclude=search,aggregator
 *
 * runs only search, archive and aggregator modules
 * http://mysite.com/cron.php?includ=search,archive,aggregator

------------------------------------------------------------------------

Wed, 23 Mar 2005 21:23:59 +0000 : Dries

Isn't it possible to run all cron functions every 2-5 minutes?  The
impact of that should be minimal.

------------------------------------------------------------------------

Wed, 23 Mar 2005 21:33:06 +0000 : moshe weitzman

an alternative approach is to make a quick PHP page which simply calls
mailhandler_cron and any others that need to be called more frequently
than normal. then call that php page from cron every couple minutes ...
not so sure this complexity is worth having.

------------------------------------------------------------------------

Thu, 24 Mar 2005 07:32:32 +0000 : robertDouglass

Whether or not this "complexity" is needed depends a lot on what you
expect to do with cron. As soon as one starts aggregating not tens but
several hundred RSS feeds or more, it is impossible to run cron every 2
minutes. Yet if the site depends on mailhandler keeping user moblog
submissions current, 2 minutes is already about the maximum latency
time acceptable. Thus the need for crons on different schedules.

In terms of usage, writing 

  ?include=mailhandler,search,event 

isn't so complex. On the code level, splitting that list on comma and
looping over the resultant array also isn't really that complex. The
patch defaults to normal behavior for people who don't need the
feature, and I've seen more than one site that had to solve this
problem.

------------------------------------------------------------------------

Thu, 24 Mar 2005 10:48:09 +0000 : Robert Castelo

Could different cron runs be set to run different tasks based on a cron
ID number....

For instance, set up 3 separate cron to run every hour, each one calls
the cron.php page including a number variable which runs a certain set
of tasks.

An Admin control panel would list all cron tasks and allow
administrators to split them into separate cron runs based on the
number variable passed to the script when calling cron.php.

------------------------------------------------------------------------

Thu, 24 Mar 2005 11:24:53 +0000 : robertDouglass

Robert,

the id parameter is already a practical necessity for this patch if
cron_busy is to be effective. I'm open to suggestions as to how we
would track various cron tasks and whether they are busy.

First things first, though: does anyone except me need this?

I'm not going to program an admin-configurable cron mechanism unless
there is demand for it. Furthermore, such a system would really be
incomplete unless there were some actual mechanism for setting these
cron runs up from the admin interface as well. This wouldn't be such a
bad idea, I know a lot of people who still type /cron.php into their
browser every day or so to updated thier sites (yes I've mentioned
poormanscron). Anyway, first reactions to this patch have been cold, so
maybe nobody wants it.

------------------------------------------------------------------------

Thu, 24 Mar 2005 11:39:13 +0000 : Robert Castelo

+1 from me.

I'll be needing something like this once my email newsletter is
released and starts hogging cron runs.

------------------------------------------------------------------------

Thu, 24 Mar 2005 16:06:31 +0000 : Chris Johnson

It does seem like a good idea to allow running different cron tasks at
different intervals, so as to be efficient and reduce web server loads.
 There is little point in running tasks that do not need to be run. 
Many cron tasks only need to be run once to a few times per day.

Note also that cron job scheduling on most Unix-variants is only within
a +/- 1 minute range, so trying to run a cron program every 2 minutes is
approaching the crumbling edge of being "on time."

------------------------------------------------------------------------

Thu, 24 Mar 2005 16:37:39 +0000 : robertDouglass

I think I am leaning in favor of extending cron.php in the following
way:

1) Add admin screen which scans all modules for existence of cron hook
2) set a cron_interval variable for each one
3) allow admin to set an interval
4) check whether the current cron run falls outside of each module's
interval before invoking its cron hook
5) before a module's cron hook gets called a {module_name}_cron_busy
variable gets set. This would function like the current cron_busy now,
just at a modular level.

The admin would then set one cron tab to run at the smallest needed
interval and could then decide on a module-by-module basis how often
each is to run.

How does this sound to people?