AMD AM1 Kabini Part 2: Athlon 5350/5150 and Sempron 3850/2650 Tested
by Ian Cutress on May 29, 2014 2:00 PM ESTSynthetic IGP Benchmarks
Unity – Graphic Scene 720p: link
As part of my IGP testing I went searching for a couple of new Unity based benchmarks to help decipher the line between the desktop graphics solutions and those that are not so great. First up is a graphical humdinger, implementing a complex scene with lighting effects (including fluid simulation, shadows, SSAO, Bloom). We run the benchmark at 720p with the highest graphical settings, reporting the average FPS.
Unity – Draw Calls: link
Next up is a benchmark limited by draw calls rather than rendering complexity. The scene generates simple Nintendo Gamecube polygons that fall due to gravity and bounce around until stationary. The scene continuously spews out these polygons until three consecutive frames fall under a 20 FPS average. We run the benchmark at 720p at simple graphic settings to minimize the graphical complexity, and take the average of several runs.
3DMark
The synthetic tools from Futuremark have been on the benchmarking landscape for over a decade, with each generation designed to tackle new problems as either the CPUs or GPUs become too powerful. Here we test 3DMark 06, 3DMark 11 (Performance), the latest 3DMark and 3DMark Vantage’s pixel/texel tests.
Tessmark
The latest version of TessMark is designed to focus on tessellation via OpenGL 4. We run the latest version of the benchmark using the high resolution map set at maximum tessellation while 1080p full screen, reporting the average FPS.
Facebook
Twitter
RSS
87 Comments
View All Comments
Ian Cutress - Thursday, May 29, 2014 - link
I've adjusted most of the severe cases into graphs that are easier to read :)easp - Thursday, May 29, 2014 - link
Better, but dude, the red bars stand out, and yet they represent something other than the focus of the article. Given the color pallet, I'd assume that the black bars were the least significant numbers, the background information, and yet, they actually represent the focal point of the article.Ian Cutress - Thursday, May 29, 2014 - link
I originally have had blue for Intel and red for AMD. Black is the only other color I can add that doesn't look odd; if graphs start having three-plus colors then it just looks a little odd. It might be worth greying everything and just highlighting the important points without an Intel/AMD distinction except in the labelling for the future.edzieba - Friday, May 30, 2014 - link
How about adding 'cores' to bars that are immediately relevant to the articke (e.g. an orange line in the centre of the bars for the socketed Kabinis and the Celerons). This would highlight the bars that are being compared directly, while still being in the context of all the other data, and keeping the expected blue/Intel red/AMD bar colouring intact.DanNeely - Friday, May 30, 2014 - link
Thanks, that's much better.pjkenned - Thursday, May 29, 2014 - link
Ian - good to see you had similar results as I did. The other bit is that the J1900 can be passively cooled while the AM1 chips need active coolers. That helps lower power consumption, noise and points of failure.I think I had benchmarks with the Raspberry Pi also - these are MUCH faster.
buffhr - Thursday, May 29, 2014 - link
Would have been nice if you could have included some hd video playback (1080p/720p/3D) and impressions.vesoljc - Thursday, May 29, 2014 - link
I second this!nirolf - Friday, May 30, 2014 - link
Me too! Should be fine, but what about 4K?BMNify - Saturday, May 31, 2014 - link
"but what about 4K?"what about it!, it doesn't really exist for consumers, oh perhaps you mean pseudocolor UHD 2160p, or the real colour UHD-1 3840 pixels wide by 2160 tall at 10bit or 12bit per pixel content today as used by several ARM Cortex Soc