"Around 50% faster."... a much more impressive statement v.v. AD Vina sciences [All of them], is "Twice as fast!" (it's higher in fact) as windows takes more than 2 times as long to process OET1 compared to Linux

The Haswell renditions are more energy efficient and coming down in price as they've been overtaken by Skylake, and since energy is the ever returning cost [with the accompanying reduction in heat generation, speak cooling needs], another important factor to consider [I'm so happy with me now over 2 years old 3770K ;].

Actually as far as the computer choice is concerned, I would have said get a nice i7 6700T (insisting on "T"!) on a good motherboard combined with 2 nice AMD 380 OC Nitro GPU coupled with lovely 4 gigs of DDR5 (quite as expensive as 2GB, so why go for less?) BUT since GPU-crunching isn't a topic here at WCG these days, you need to look around for other hardware... or other projects On that PC, by definition your "gaming-PC" as you called it, I'd set up dualboot with Win10 for gaming and Linux to crunch over-night... (needs reboot though...) If you can afford, go with R9 Nano. My hint: For crunching, choose AMD, for gaming, go with Nvidia. Up to you what is the MOST important about what you want to do... better frame rates in games VS better crunching...

Now about OET1 itself: For that(!) project, I only go with dedicated 8-core Mediatek on Android (4.4.4 and 5.0). Result stats below show how well ARMs do in OET1 can be found here (It also include minicomputers running on various Linux-distributions):

http://wuprop.boinc-af.org/results/arm.py?pro...n=Outsmart+Ebola+Together

(The lower the number is, the better it is: The numbers represent the average hours(!) needed to crunch one OET1-unit is shown as the front number, obviously you'll get better results if your android device is dedicated and runs 24/7 without bloatware sitting in your memory. Also, if you disconnect from charger a lot, you'll find yourself on the slower end of the stat. So, if used as crunching device, expect results on the faster side though. Also, I need to consider that one of my devices has 8 cores each, according to my WCG-stats, I could claim about 8 OET1-units finished in 5-10hrs... depending on the Mediatek being used... I mostly use 2 major batches of units with different crunching power... and some random other Android devices from Samsung)
I can say that energy cost on those devices can (nearly) be completely disregarded (unless you plan running clusters)

My other x64-units crunch the other projects... like FAAH2, CEP2, MCM and UGM. Otherwise I'd pretty much feel like crunching on an x64 what could otherwise could be done on GPU... kinda inefficient! If one of those mentioned projects becomes available for GPU, like FAAH-VINA back in the "good old days", I'll take that project immediately off my "CPU-crunchers list". I'll go with whatever will be most efficient as far as electricity bill is concerned. Same feelings for me about OET1 on ARM/x64.

By the way, great Boinc-stats project, runs as non-CPU-intensive. Everybody should sign up there...

joneill003 - http://wccftech.com/amd-zen-opteron-processor-32-core/

I'm really looking forward to Zen and hoping for a desktop 16-core version :D

well, about WCG, here a thing...to have most on WCG, you only need to have "most cores on CPU"...so:
1. use most modern MBO, for most modern CPU family...regardless if it's a AMD or INTEL...but I'd choose INTEL for mine, 'cause the have a higher Tjunc...so more reliable in temp. they are!
2. don't spend too much money on CPU...all you need is a proc with highest number of cores, so that you get most time on WCG! doesn't have to be fastest proc, just the most cores...& preferably with HT, so that you get 2x time of cores!
- also, you can always upgrade to faster CPU, in a year or two...postponing new config all together!
- p.s. some proc have intelHD with openCL enabled...so you can have 2x GPUs on your machine! & that rules of XEONs...
3. about GPU, you'd probably best stick with nVidia...it was 1st enabled here on WCG, so probably it will be again here on WCG! it also have a CUDA & openCL enabled, so it will get both of both worlds...
4. definitely use SSD
5. RAM, use slowest DDR3...'cause there not much performance issues in using fastest DDR3, while they get quite a pricey!

Hope this helps out!