Another question would be..
What if they're both doign the full loads?
ie: Lets make up scenarios closer to reality.
An common old school emu would be a CPU core running (dominating) the main thread; it handles the emualtion run, plus GUIs and such; the second core would be doing the sound thread and not much else.
The main core would thus be in a busy read/write tight loop, while the audio thread would be small-read/big-write (where 'big' is not all that big
ie: Splitting a CPU emulator across cores would be ugly and not likely to occur; running a dual-cpu VM on a dual-core could be easily ('naturally') partitioned, but lets worry about that later.
The question is.. does the CPU emulator performance tank as a sound theread fills up the buffer?
Answer.. not too much I imagine; memory bandwidth is shared to the cores, but I doubt a sound core would hit it all _that_ much.
Now, a cpu emulator on each core.. that could slow things down a bit.
But lets cut to the chase.. being stuck at 200, or being stuck at dual-200? Obviously we'll get some improvement, and its not going to be perfect (400).. more likely around 200+(0-150) depending how well used, effective throughput?
Don't listen to me, I'm seriously wiped out
jeff