I do not think the distribution model is favoring High Performacne machines. I have an i7-975 and an I7-965, both High Performance, very reliable machines that do nothing but crunch WCG 24x7. They have each recieved only about a dozen WUs, since the beginning.

I have 96 cores, working on WCG and I have only recieved 296 WUs for a total of 55 days and a silver badge. So I have no idea how some else has got saphire already.

At least HFCC is now getting a lot of work from me with now over 15 years worth of work contributed while I wait for DDDT2. If it ever breaks free I could get Saphire in 8 days!

Yep, right now 147,978 done, about 44 million more to do.
Remember that uplinger's now famous reference chart gives numbers before applying the necessary dual redundancy.

That leaves hope, no?

What has happened is that people connected to DDDT2, like you, got a reasonable number of WU for the supply that was available.

At the same time, there were people who happened on the WU release and upped their buffers at the time. With the release spanning 2 days, they were able to pull the max of 80 WU x 2 days x number of cores and since the WU release had a finite number of WU, the distribution got skewed.

Add to that was that the WU release was metered out slowly, so people connected to multiple projects pulled down a WU from another project to fill their normal buffer because there was often no DDDT2 WU when they polled the server. The only people who got a large number of WU were people who had only selected DDDT2 and they were either just plain lucky or they have no life and were waiting to pounce.

Favouring exists, and I think it should at this stage; to speed up the project, to the point where everyone can contribute, but the project has been undermined by badge hunters that set their cache to 10days and then fail to deliver. This is a serious problem and the way it has been handled, or not, is disturbing.
During the "55days"€ I had about 30cores attached 24/7 and was only running one other project. I got less than 200 tasks all in. I also had about the same number of cores running part time. A lot less than the 5000+ tasks I could have got by massaging the buffers.
I dont like the way grabbing these tasks effects other users with only one or two cores, or the way it slows the research down, so I wont be contributing to the badge grab culture WRT this project - I would prefer such users were not deterred to the point that they leave. The same applies to the Betas; I will on occasion try to get a few work units, but I will not set my cache to many days. Doing so deters participation and is an overall negative for WCG.
Hopefully the next time tasks are to be released, I will see an announcement for new tasks; that way I will set my cache to somewhere between 1 and 2 days and get plenty of work units -€“ and hopefully prevent some from filling their cache with 10days worth of Work Units. My tasks will of course actually return well within that time, rather than fail to complete in time, which has been the case with other users trying to grab too many tasks. This project has been slowed down enough as is. When tasks fail to return in time, as has been happening since the outset, they have to be re-issued. This delays the next stage unnecessarily.
Be reasonable, you will get a Blue badge in due course.

The Deluge begins ..??

I hope so I just want to crunch and achieve my goals..

Heheheh very sneaky putting the project on line just as Europe is waking and the Americas are sleeping.