If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

I somehow had the idea the open source drivers would be CPU limited. No multithreading with catalyst too, load < 25% for a 4 core CPU? I asume 100% is full CPU utilisation. Would be great if one of the driver developers could comment on this.

To the Phoronix and Michael critics: Stop derailing the thread! Want to whine about it? Get you a fscking blog!

I think you might be right. Single threaded apps will have a lower cpu utilisation - would be great if we could see the utilisation of each core during the test

about the whiners i dare you to point me out another site which at least has 10% of the information richness about linux and alikes
beside phoronix (The H maybe but most articles about OSS are from phoronix and linux.com follow the same direction)

I somehow had the idea the open source drivers would be CPU limited. No multithreading with catalyst too, load < 25% for a 4 core CPU? I asume 100% is full CPU utilisation. Would be great if one of the driver developers could comment on this.

To the Phoronix and Michael critics: Stop derailing the thread! Want to whine about it? Get you a fscking blog!

I think the issue with the OSS drivers isn't doing lots of math or other calculations on the CPUs. It's them sending/fetching data to the GPU and then sitting there waiting on it before it can do anything else. That ends up showing the CPU as idle instead of busy, but it's waiting and can't do any more work.

I expect the higher CPU usage with Catalyst is mostly due to just pushing a lot more data to the GPU because of the higher performance, but it's also possible that it does more work optimizing everything in the driver and that ends up costing it more than the simpler OSS driver.