If you seriously think disabling one of the ALUs in a module is a good idea, I think you seriously need help. Disabling an ALU will effectively halve your total integer ouput. Much as the url in abitom's post demonstrates, performance is lost, not gained. There are plenty of benchmarks out there that put the 'disabling half your ALUs yields performance increase' myth to rest.
AMD didn't probably beat Phenom II significantly, it DID beat Phenom II significantly, as much as many people would like to disagree, the truth can't be changed. I own three Phenom II X6s clocked to 3.5-3.8GHz each. They are all 3x slower than my FX-8120 @ 4Ghz with stock voltage at x264 encoding, they are twice as slow in compiling source code in Linux using make -j9 than Phenom II X6s with make -j7, and if you compile your own source code with -march=bdver1 you are looking at potentially 2-3x faster computations in these programs, though depends on what kind of calculations this program is doing.
There are two primary problems with the current generation of FX. The first is that most compilers software makers are using do not support AMD at all, if you use an AMD processor, it might as well be running in Core 2 Duo mode, instruction set-wise. There are a few cases where you may find someone is actually properly compiling their software, aka x264 encoder, but you'll find all benchmark software not on Linux is compiled with Intel C+ which cripples performance to abnormally low results. The second is the cache issue, which hopefully has been addressed with Piledriver. I don't see why AMD wouldn't fix it since they are aware of its existence.
But finally, a lot of AMDs problems is Windows, no joke. Install Linux and you'll never have problems, even old Phenom IIs may receive double the performance due to software actually being compiled correctly. Windows programmers just suck at programming.
I foresee great success with Piledriver.