OK, that had me scratching my head in confusion. A couple of Google searches finally gave me what I think is your meaning. By PGO'ed version.... I assume you mean you developed a "profile guided optimization" version of the MB CPU app? Is that something like you do with profiling in your SoG app? If so, I would think that could provide a major improvement in computation efficiency. I think you hinted at that in your note. If I am more confused than usual. .... please correct me.Seti@Home classic workunits:20,676 CPU time:74,226 hours

Nothing in common with SoG.
Just new x64 CPU stock build expected to be faster than current one.
But cause big numbers of CPUs involved here its impact on project performance may be comparable with SoG introduction indeed.SETI apps news
We're not gonna fight them. We're gonna transcend them.

I would just allow CPU work for beta project.
Only if after let say ~2 weeks there is still no attempts to download new version worth to start abortions.
Of course, if host already has many completed results for x64 8.05 it's no harm to speedup things a little (on beta!) and abort CPU 8.05 to get CPU 8.06.
If no CPU work completed before one needs to complete BOTH 8.05 and 8.06 to have useful results for this testing.SETI apps news
We're not gonna fight them. We're gonna transcend them.

Thanks Raistmer, but since this was just an experiment for me, I immediately set NNT after the first slug of 8.05 tasks. I had previously set up Beta for just CPU. After I aborted the 8.05 tasks which Zalster recommended, the next request for work got me half and half 8.04 and 8.06 (alt) task. I just aborted the 8.04 tasks and have about 13 of the 8.06 (alt) CPU tasks to work through.

From what I saw with the 8.05 (x64) app, I wasn't impressed. It was definitely slower than the Lunatics 8.00 AVX hand optimized app by Joe Segur. Hope the 8.06 (alt) app can match the AVX app speed.Seti@Home classic workunits:20,676 CPU time:74,226 hours

If no CPU work completed before one needs to complete BOTH 8.05 and 8.06 to have useful results for this testing.

Oops, sorry. Didn't know that you required BOTH 8.05 and 8.06 (alt) for comparisons. Thought that 8.05 had been around for a couple of months already and you already had the baseline.Seti@Home classic workunits:20,676 CPU time:74,226 hours

From what I saw with the 8.05 (x64) app, I wasn't impressed. It was definitely slower than the Lunatics 8.00 AVX hand optimized app by Joe Segur. Hope the 8.06 (alt) app can match the AVX app speed.

Void comparison.
Joe's binaries were for version 7 of MultiBeam. We on version 8 currently. So, his binaries can't be used no matter how fast they are.
Current AVX opt build is my M$ VC based one. Most probably it's faster even than this build but again, they have different area of usage.
Stock is to work everywhere, AVX opt for manual installation on AVX-only hosts.

So, we don't compare opt and stock here. We compare x64 8.05 and 8.06 ones between each other (and do this for the reason).SETI apps news
We're not gonna fight them. We're gonna transcend them.

Hmmmm, significantly slower so far. Unless they make like bandits for the last 50%. Might have something to do I guess with my inferior AMD FX performance compared to Intel.Seti@Home classic workunits:20,676 CPU time:74,226 hours