HST is a quorum of 2 project, I'm usually paired with another who claim more in line with what is granted. I know there is a rule when claims of the two in the quorum differ a lot, I wonder what will happen if I'm paired with another who also just claim 60.

But you are saying that for this project we get what the server has calculated, not what the clients claim?

What's annoying is that the 'claim' gets replaced by some minimalistic value because of some claim ceiling that got passed rather than some average that's going for a science. Because of the 60, the wingman will get a knock on the head too as 400+420 average is 410, but 60+420 is 240.

As it is, we don't get the data to do a proper analysis and work out a solid functioning solution, but that is what we were told by the techs here, they're going to do zero unless someone comes up with a thorough replacement. End of story.

Anyway, you can calculate the claim before WCG put their hands on it by taking the benchmarks Whetstone and Dhrystone, sum them and divide them by 480. to get the claim per unit of time and multiple that by the CPU time, so for example 3000+9000 / 480 * 3 hours would be about 75. Some specimens in past went into the client_state file and pimped the benchmark values, which is the origins of why the benchmark is not taken for granted.

HSTb jobs are good for about 400-450, depends on the 4 run types that seem to exist T300, T325, T350 and T400. Do not recollect seeing any other, each having a fairly regular run time.