I understand the basic scheduling problem of the task. However, it seems improbable that s single site or even a few sites would cause this dramatic and consitent a change in processing time.
If the change in time was due to variable sites and their log files, the time would fluctuate constantly. However, for the last many months, the processing time has been 2:06 AM, reliably. And now it’s 2:53 AM, reliably.
I think it’s a change on the server. I would appreciate an investigation. If I thought submitting a ticket would result in some real action, I would do so.
Since your last post Stephen, the AWStats processing time has returned to 2:06 AM (2:04 AM last night). So it seems that is has returned to the previous reliable performance.
Clearly something changed and you changed it back. What was it?