Optimizing every cron run is overkill.

It is better to have a variable and a settings option to specifiy how frequently optimize should run.

Comments

simbot’s picture

simbot commented

Possibly. I mean I will add this option in, along with the ability to select the tables which are optimized, etc. But I didn't find optimizing to be a time consuming task.

I guess what I'm getting at is, what should the default minimum time between optimizes? Should it maybe be decided by the level of overhead in the tables?

kbahey’s picture

kbahey commented

Just put a drop down list with 1 hour, 6 hours, 12 hours, 1 day, 2 days, 4 days, 1 week, 1 month

Use drupal_map_assoc to create the list, and let the admin decide how often to run that. Default to something reasonable (once a day)?

deekayen’s picture

deekayen commented
Category: bug » feature

I only run my cron.php file every 4 hours. I know I wouldn't choose 1 hour because cron.php wouldn't run that often, but if I did, and it didn't run every hour (since it wouldn't), would that be a bug or just a documentation issue? What might be a different option for selecting frequency that could account for varying cron.php execution frequency?

deekayen’s picture

deekayen commented

Re: selecting which tables you want, please test http://cvs.drupal.org/viewcvs/drupal/contributions/modules/db_maintenanc...

I'm trying to consolidate Optimize and DB maintenance into one.

deekayen’s picture

deekayen commented

http://drupal.org/project/cronplus is a decent solution for this.

deekayen’s picture

deekayen commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.