I don't think stats have been run for December 1 and 2.

I rather suspect that the stats gathering happened as per usual, but whatever prepares the display pages didn't start up and complete its work before the stats pages became visible. This "show it before it's ready" thing also seems to affect the user Results pages, possibly because the API services aren't fully started either[*1] -- it would be interesting to know whether that is what's happening, especially if it can be avoided during a controlled restart, but who knows?...

On a similar note, the three ARP1 stats files were generated in a timely fashion on both occasions during the 40 or so hours of the outage, and their content appears reasonable. Gathering that stuff is also a non-BOINC function that seemed to be unaffected :-)

Cheers - Al.

*1 -- I see this whenever there's an unplanned non-BOINC outage, as the forums often return 10 or more minutes before I am able to use the APIs to pick up statistics missed during the outage; the necessary authorization connections don't seem to get made at first (but forum access knows who I am, so the authentication stuff is running!)

Looks like Krembil has revived the WCG youtube channel.
https://www.youtube.com/@worldcommunitygrid7090
Go enjoy some videos.

I hope everyone enjoys their break and backup projects, I'll see you back here in the new year !

On stopping WU creation - what follows is just my view, and I'd be interested in any counter-arguments, not that it makes any difference to their decision on this occasion :-) but policy might well be different for future (shorter?) planned outages!

Unless running a hacked client, I don't think it would be possible for most users to accumulate work enough to see them through such a long outage (especially if tasks aren't being sent out with vastly increased deadlines!), and if that's not possible I wonder if there's actually any point in trying to facilitate running [extra] work during the hiatus.

The more work out in the field when the servers go off, the more likely it is that there may be issues with retries backing up, even if they are only for tasks that suffer genuine errors or get aborted client-side. Tasks being sent out now still show the classic 6 day deadline at the client side, so "Not Started By Deadline" will still happen to some tasks, and the more sent out, the more will end like that...

So I reckon it makes more sense to try to minimize any post-hiatus recovery issues that might arise... And hopefully some of the data centre changes after the restart will allow the sending of larger amounts of work than we'd been seeing for quite a while, so the volume of work processed won't suffer in the long term.

Cheers - Al.

P.S. I guess a few users will take advantage of the outage to save on their electricity bills for a while -- I just hope they return :-)

I used to hoard Seti WUs before a shutdown. The Seti WUs on my old old machne would take 23 hours, so it didn't take many to keep me busy. I would then set my machine to no upload, until the system had been up for a few hours and the backlog had cleared.

It isn't worth hoarding MCM as they go so quickly. I would stock up on ARP if they were available. It isn't important to keep my machine busy for a month, but each ARP done is important as it is iterative. I wonder if there would be resends with a whole month to get them done.