Yes 20 MCM on my 3900x and 10 on my 3600x.

Also the SCCs are mostly 30 minutes on my 2 Ryzens so this may be why there are so many SCC units completed per day. MCM ~ 1.30hrs
Yes no babysitting for about 1 week

I have to agree with you. I am also getting around 30 minutes on my Ryzen 7900X Windows 11 pro 22H2.

I was hoping it was a surge of tasks waiting for "validation" or "verification". For me very few of my over 200 waiting results have moved

In reply to hchc 's post above:
[Screenshot snipped, but I observed three _0 tasks for MyoD1-C...]

Yup, sorry -- I could've been a bit more clear there; I was only intending to count retries triggered by the validator, and I suspect a lot of your Pending Verification items were Adaptive Replication rejections that got a _1 retry that then failed No Reply or otherwise and the next retry was triggered by the transitioner, not the validator! Without access to workunit numbers, checking the actual progress of tasks is purely speculative, of course :-)

Here are a couple of examples of WUs from the 16th, one for each case. Dates are UTC, and I've used NSD to indicate a task that returned an Error about the time the deadline ran out with just the client version reported (WCG doesn't seem to flag "Not Started by Deadline"...)

SCC1_0004193_MyoD1-C_75946 (WU 353852073 created 2023-08-14T21:02:16
  Task _0  Sent 2023-08-15T18:06:47  Returned 2023-08-16T01:50:59   Status Valid
  Task _1  Sent 2023-08-16T01:51:25   Returned 2023-08-17T17:24:30  Status Valid

Task SCC1_0004192_MyoD1-C_90798 (WU 354208821) created 2023-08-15T01:17:14
  Task _0  Sent 2023-08-15T23:55:43   Returned 2023-08-25T23:52:32  Status NSD
  Task _1  Sent 2023-08-15T23:55:52   Returned 2023-08-16T04:59:00  Status PVal
  Task _2  Waiting to be sent

Note how the first one presumably went straight to a validator request (which didn't declare the result canonical, thus causing a retry) whilst the second one (which is still stalled!) hasn't yet been seen by the validator... Without access to the WCG validator code it is not possible to look at what [extra?] flags might be being set on an AR rejection, but the retry requests for the two cases are almost certainly going through different code paths in the transitioner :-)

For what it's worth, I currently have 4 SCC1 tasks Pending Verification -- all of them are FLI1-B tasks that were singletons that didn't get AR validation, and all four currently have confirmation retries in progress (all of which issued within an hour.) I also have 10 waiting for a task to be sent, but those are all Pending Validation.

Sorry for any confusion...

Cheers - Al.

P.S. My experience of tracing code for AR validation is based on looking into MilkyWay code as an outside observer when they had serious problems after a major disk crash. Someone else may well have more/better experience :-)

Well, come Tuesday morning after a long weekend, and it seems that MCM1 is in short supply as well... :(


Ralf

SCC1 is out of work even before the weekend.

Mike