Travis, can you reduce the credits of two hosts got 2x250k and 700k credits / WU? These are the 2 ones on top computer list, we must fair enough but there are many other too but not so extremely.

Take an average across different os and cpu's of "claimed credit" in benchmarks...

Thats probably a good idea. The work units are (for the most part) fixed size, so fixed credit might be the way to go. Currently, the amount of work done is based off two things: 1. the size of the volume, and 2. the number of stars.

Between a quorum of 2 and a way of calculating credit not based off boinc's benchmarks, maybe that will fix the problem?

The High Benchmarks could be causing a problem if that is how the Core client figures out scores. That is an Old version of BOINC and was known to cause weird results. They did not cheat but should update their Boinc client to a newer version.

Version 5.10.20 had no problems with correctly benchmarking a CPU.
The BOINC versions that possibly gave weird outcomes due to benchmark inconsistencies were 5.8.17, 5.10.1 and 5.10.6

None of the above versions gave integer benchmark claims in the way the two clients in this thread have them. So either someone took the core client code and adjusted how the benchmarks should be done before compiling it as a 5.10.20 client (easily done by changing the version number before compiling), or they've changed their values in client_state.xml