[Galaxy Note GT-N7000 Android Development] Formhault:
NoteCore V8 & V9, standard & extreme extended testing

Okay, so here's what I did. I tested V9 standard and V9 extreme with some benchmarking applications, for several times. I know benchmarking is overrated, but for what it's worth, here are my results, so I'd spare you the work of testing yourself :) .

Also, I've heard/seen the hype going on about the fact that the kernel needs some time to stabilise/settle in... Well, while that may be true, the testing began 2 minutes after the phone finished booting the first time (after Sybr Kernel Cleaning script + kernel flash), so... results should be pretty much accurate, I'd say :) . It's not like I let the phone settle for 1 hour on one kernel before starting testing, while the other kernel only had 5 minutes to "take a nap". No. Testing started 2 minutes after the first boot, in the order below.

I ran AnTuTu, NenaMark 1, NenaMark 2, Quadrant Standard and Linpack for Android for three times each - except for Linpack, which got 5 turns - and here are the results. If it matters, AnTuTu was set to test the internal SD card, but I don't see any resemblence of it in the score, so... I dunno.

For what it's worth, Wi-Fi was on (router = 3 meters away). Network was on 2G/3G automatically (3G signal steady @ full). ROM : CleaNote V4.

V9 STANDARD

AnTuTu #1 - 6651 total. CPU : 3093 ; GPU : 1448 ; RAM : 1220 ; I/O : 890.

AnTuTu #2 - 6419 total. CPU : 2935 ; GPU : 1458 ; RAM : 1137 ; I/O : 889.

AnTuTu #3 - 6013 total. CPU : 2684 ; GPU : 1458 ; RAM : 1073 ; I/O : 798.

NenaMark 1 - 56.7 fps ; 57.2 fps ; 57.3 fps.

NenaMark 2 - 43.7 fps ; 42.3 fps ; 43.2 fps.

Linpack (MFLOPS)

Single thread - 54.121 ; 54.829 ; 51.337 ; 54.615 ; 54.579.

Multi-thread - 84.46 ; 82.518 ; 88.215 ; 88.446 ; 87.619.

Quadrant #1 - Total : 3990. CPU : 5886 ; Mem : 2439 ; I/O : 8524 ; 2D : 971 ; 3D : 2132.

Quadrant #2 - Total : 3580. CPU : 6513 ; Mem : 2756 ; I/O : 5549 ; 2D : 962 ; 3D : 2121.

Quadrant #3 - Total : 3476. CPU : 6370 ; Mem : 2220 ; I/O : 5736 ; 2D : 952 ; 3D : 2100.

**Quadrant #4 - Total : 4518. CPU : 6350 ; Mem : 3503 ; I/O : 9635 ; 2D : 952 ; 3D : 2148.**

**Quadrant #5 - Total : 4103. CPU : 5913 ; Mem : 2722 ; I/O : 9018 ; 2D : 952 ; 3D : 1908.**

V9 EXTREME

AnTuTu #1 - 8059 total. CPU : 4092 ; GPU : 1476 ; RAM : 1591 ; I/O : 900.

AnTuTu #2 - 8078 total. CPU : 4095 ; GPU : 1472 ; RAM : 1621 ; I/O : 890.

AnTuTu #3 - 8073 total. CPU : 4091 ; GPU : 1468 ; RAM : 1615 ; I/O : 899.

NenaMark 1 - 57.0 fps ; 57.3 fps ; 57.3 fps.

NenaMark 2 - 51.1 fps ; 51.6 fps ; 51.4 fps.

Linpack (MFLOPS)

Single thread - 61.87 ; 61.961 ; 49.083 ; 58.461 ; 61.191.

Multi-thread - 83.087 ; 80.471 ; 89.908 ; 85.792 ; 83.375.

Quadrant #1 - Total : 4981. CPU : 7484 ; Mem : 3877 ; I/O : 10186 ; 2D : 952 ; 3D : 2408

Quadrant #2 - Total : 4964. CPU : 7472 ; Mem : 4299 ; I/O : 9726 ; 2D : 971 ; 3D : 2350.

Quadrant #3 - Total : 5023. CPU : 7455 ; Mem : 4056 ; I/O : 10334 ; 2D : 952 ; 3D : 2319.

Note on Quadrant Standard results - V9 EXTREME

My device was ranked on the first place, above the One X and Transformer Prime, in all three tests I ran. By looking at the graphic, the One X scored ~40% more in CPU, ~20% more in RAM and ~50% less in I/O. The 2D / 3D scores were almost identical - maybe 1-5% difference. You get the idea :) .

Seems like Gavin did a much better job at tinkering with the I/O schedulers than HTC developers, haha. The increased score in CPU/RAM is to be expected, obviously, since the One X sports a CPU that holds twice the raw processing power...

Note on Quadrant Standard results - V9 STANDARD

My device was ranked the third, just below the One x and Transformer Prime, and on one occasion (another test I ran sepparately right now - test #4, in green), ranked between the two. I figured it was a mistake, so I ran another two tests, and the results were similar to #4! I figured I should reboot the device and make another Quadrant test. After I rebooted, the results were still similar (see #5).

I was hoping I could get results similar to the first three Quadrant tests on the V9 standard, so I could compare them with the One X scores... but nevermind. Not sure if the whole Quadrant test was compromised, and I should've rebooted, waited a bit more, then re-run the tests again... I'm not gonna do that now.