17seconds :
Auto PhysX never uses the CPU. Firestrike does not use GPU PhysX acceleration and therefore says nothing about the performance of a dedicated PhysX card.
Using a low 720 resolution is going to highlight the effects of CPU bottlenecking and negate the advantages of dual cards in a SLI configuration. Naturally, at such a low resolution, your single card will run at just about the same speed as two in SLI, particularly when paired with an underpowered AMD CPU.
The tests concluded that when running the CPU dedicated for physx the benchmark scores were about the same as when on Auto. Hard to believe it doesn't use the CPU when on auto, when putting the 1st or 2nd card for non dedicated physx usage changes the scores a noticeably higher. If on auto it doesn't use the CPU then it's odd that the scores are so much different than selecting a non-dedicated card to handle physx.
Also, if physx isn't a factor in 3dmark benchmarking then I don't know why I got such a big improvement when I put dedicated PhysX to one of the cards. I tried every scenario possible and this was the only one that got a big boost in FPS.
However, I will agree not all programs and games will benefit from dedicated PhysX but from running 3d Mark Firestrike it would seem that graphic intense games that are big budget releases, will probably have the manpower behind it to code to the correct standards for Nvidia cards and people will see an improvement. If anything, if someone is trying to improve game play, it's probably worth a try.
I have yet to run any in game FPS, will fraps help verify my FPS with different settings or is that null and void too? I'll report the findings of in game FPS soon.