That's normal when you switch from no-redundancy projects (where most WUs are credited immediately) to a multiple quorum project where you will first have to create your buffer of results waiting for being validated and credited that the wingmen have returned their results.

Once things are stable after a few days you can really see if the new project is crediting more or less per hour. For HCMD2 I think it is usually rather more than less.

Happy crunching. Jean.

You post so little to give any chance of an accurate advise. First look on the RS (Result Status) at the WU (Work Unit) detail. It's a quorum 2 project so it's easy to see when the wing(wo)man has turned in the result too. Then, post the name of the task... is it a parent, is it a child, is it a grand child, is it an über grand child? Latter have a higher potential run to run short since they are bound to do much less positions.

This is an example of a grand-child.

positions 139791-140172 is the child task ran previously
positions 139938-139985 is a grand child, client doing the child managing 148 147 positions.

Given that 139986-140172 were not included in the grand child task it means the work will pass likely for the remainder into a great-grand child, or maybe there's another grandchild already doing that range. Don't know, but given it took only 24 minutes, not sure why yours only had 47 positions in it. Something for the techs to worry about as they are the ones ensuring all positions are done for a protein-protein test.

I have some WU completed in 18 min.

Have had a wide variance in completion time also. As the project progressed from inception, it appeared, on average the time to completion increased.