Sony UX1XRN benchmarks

Disclaimer

This article is not a comprehensive performance analysis of Sony UX1XRN. The goal is to find a comparable PC configuration for gaming. And we will mostly compare performances of CPUs and GPUs.

Testing methodology

The following programs were used to test CPU and Memory performance:

  • SiSoft Sandra version 2001.0.7.10;
  • PassMark Performance Test 8.0 build 1054;
  • PCMark 2002 build 100;
  • Unreal Tournament version 436.
    • Settings: software rendering, resolution: 800×600, color depth: 32 bit, graphics level: high; demo file – UTBench.
    • Metric: Avg FPS.

The following programs were used to test Direct3D performance:

  • 3DMark2000, version 1.1, build 340. Settings: default values except color depth and resolution (mentioned in the results below);
  • 3DMark2001 SE, build 330. Settings: default values except screen resolution (mentioned in the results below).

The following programs were used to test OpenGL performance:

  • Quake III: Arena version 1.32c. Settings: color depth (32 bit), various resolutions (mentioned in the results below).

All tests performed after suitable warm-up period.

Setup #1 description

Device: Sony VAIO VGN-UX1XRN
CPU #1 (original): Intel® Core™ Solo U1500
CPU #2 (resoldered): Intel® Core™2 Duo U7700
BIOS version: R0101N2
OS: Windows XP Professional SP3 5.1.2600
Intel GMA driver version: 6.14.10.4926

This device has been tested with two versions of CPU:

  1. The original CPU from the manufacturer – Intel® Core™ Solo U1500 (32-bit, single-core, 1.33 Ghz);
  2. The manually resoldered CPU – Intel® Core™2 Duo U7700 (64-bit, dual-core, 1.33 Ghz).

Default GPU clock rate in UX1XRN is lower than it’s "true" value (400 Mhz, according to the specifications). In order to achieve maximum 3D performance I used GMABooser version 2.1. Technically I would not call this overclocking, because we don’t exceed the clock rate and voltage values from the chip specifications.

Thus all 3D benchmarks on UX1XRN were performed twice: with default GPU clock rate and with GPU clocked at 400Mhz.

Setup #2 description

PC setup

Motherboard: Shuttle AK38N V1.1, BIOS AK38S003
RAM: Samsung M312L2923CZ3-CB3 1Gb DDR PC2700 CL2.5 ECC
CPU: AMD Athlon XP 1800+ 1,54Ghz (used in all benchmarks), AMD Athlon XP 1500+ 1,33Ghz (used only in CPU benchmarks)
PSU: Zalman ZM1000-EBT
OS: Windows XP Professional SP3 5.1.2600

In order to find a comparable discrete PC video card I used seven cards based on
Nvidia chips:

  • Inno3D MX(200) 64MB Nvidia GeForce2 MX200 Core@176Mhz, Memory@166Mhz 64bit;
  • NoName 32M Nvidia GeForce2 MX400 Core@200Mhz, Memory@150Mhz 128bit;
  • SUMA Platinum 32M Nvidia GeForce2 MX400 Core@200Mhz, Memory@183Mhz 128bit
  • ASUS V7100 Pro 64M Nvidia GeForce2 MX400 Core@200Mhz, Memory@333Mhz 64bit;
  • ASUS V8170MAGIC/64M Rev. 3.0 Nvidia GeForce4 MX420 Core@250Mhz, Memory@333Mhz 128bit;
  • NoName 64M Nvidia GeForce4 Ti 4200 Core@250Mhz, Memory@513Mhz.
  • ASUS V9520/TD Rev. 1.02 128M Nvidia GeForce FX5200 Core@250Mhz, Memory@405Mhz;

Video cards

Nvidia drivers version (same for all test samples): 93.71

CPU & Memory performance

PassMark Performance Test results
PCMark 2002 test results
SiSoft Sandra test results
Unreal Tournament software rendering test results

AMD K7 architecture was a substantial breakthrough, which provided higher performance per Mhz than we had with Intel’s Pentium processors. Taking that fact into account, I was doubt, whether a mobile processor Core Solo U1500 is able to compete with AMD K7 at the same clock rate. As we can see now, U1500 has actually much higher performance per Mhz. In all test scenarios except one (PCMark CPU test) U1500 (which is clocked at 1,33Ghz) scores even higher than 1,54Ghz AMD K7. PCMark CPU test results are practically equal.

There is also significant difference in memory performance. Memory in UX (DDR2 400Mhz) is approximately two times faster than DDR 333.

U1500 shows outstanding results in the UT software rendering. I supposed that the drastic difference is caused by RAM. So I replaced DDR 333 with DDR 400 (NCPD6AUDR-50M26) in the PC setup and ran benchmark one more time. The result with DDR 400 was even more frustrating: 28,6 fps.

Core2 Duo U7700 is actually 2 times faster than U1500 when the test program utilizes both cores.

PCMark has failed to run the tests on Core2 Duo U7700 (the program crashes all the time).

Since Athlon 1500+ is significantly slower than Core Solo U1500, I decided to use the Athlon 1800+ in all 3D performance benchmarks.

3D performance

3DMark2000 16 bit test results
3DMark2000 32 bit test results
3DMark2001 test results
Quake 3 test results

According to the results, GMA performance is somewhere in between the fastest version of MX400 (SUMA Platinum) and the MX420.

GMA 950 at default GPU clock rate scores closer to

  • MX420: in 5 tests;
  • MX400: in 7 tests.

GMA 950 clocked at 400Mhz GPU is closer to

  • MX420: in 10 tests;
  • MX400: in 2 tests.

The fastest version of MX400 is the closest PC alternative to GMA 950 running in UX1XRN at default clock rate. But when we boost GMA 950 to 400Mhz, the MX420 becomes the closest PC alternative.

GeForce4 MX420 chip

Power consumption

Measurements of power consumption

I was curious what’s the actual power consumption of the devices. UX1XRN consumes significantly more power than I expected.

Sony UX works fine with dual-core 10W CPU. The CPU replacement increases the consumption of the device by only a quarter.

Conclusion

Athlon XP 1800+ with GeForce2 MX400 is quite close to Sony UX1XRN in terms of CPU and 3D performance. Boosting GMA 950 up to 400Mhz makes it a bit faster. In this case the GPU runs approximately as good as GeForce4 MX420.

Cortex-A8 vs Coppermine

Samples description

I made a few benchmarks of two devices:

  1. The Pandora device (based on OMAP3530).
  2. A PC with 256 Mb SDR RAM and one of the following CPUs: Pentium 3 and
    Celeron.

Both systems used the same gcc-4.4.3 and glibc-2.11.2.
Whole systems were compiled with the following flags:

PC flags:

CFLAGS="-O2 -march=native -pipe"
CXXFLAGS="${CFLAGS}"

Global USE includes sse and mmxю ffmpeg’s use uncludes mmxext.

OMAP flags:

CFLAGS="-O2 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -ftree-vectorize -fomit-frame-pointer"
CXXFLAGS="${CFLAGS}"

OMAP’s DSP was not used.

Legend

  • OMAP@600 is OMAP3530 running at 600Mhz (default for Pandora).
  • OMAP@850 is OMAP3530 overclocked to 850Mhz.
  • P3@600/133 is Pentium 3 EB (the Coppermine core) running at 600 Mhz (FSB clocked at 133Mhz).
  • Cel@600/66 is Celeron (the Coppermine-128 core) running at 600 Mhz (FSB clocked at 66Mhz).

Compilation

I want to emphasize that it is not a performance benchmark, because compilation is done for different architectures (ARM and x86). It is a benchmark of one particular task, which is essential for gentoo users.

package OMAP@600 OMAP@850 P3@600/133 Cel@600/66
binutils-2.20.1, m:s 37:50 28:45 20:06 28:23
glibc-2.11.2, m:s 177:27 138:19 104:09 145:16

OMAP3530 overclocked to 850 Mhz is very close to Celeron running at 600 Mhz.

Nbench

Nbench is a synthetic performance test.

The used version: nbench-2.2.3-r1

index OMAP@600 OMAP@850 P3@600/133 Cel@600/66
memory 3.040 4.364 2.811 2.745
integer 3.073 4.365 2.761 2.751
floating-point 0.533 0.761 5.477 5.268

Nbench does not show any difference between Pentium 3 and Celeron, which is strange.

MPlayer

MPlayer was used to measure video decoding time.
The used version: mplayer-1.0_rc4_p20091026-r1
Command line:

mplayer -benchmark -vo null -nosound input_file

Input files: Big Buck Bunny at 480p in MPEG4, H.264 and Theora/Vorbis.

codec OMAP@600 OMAP@850 P3@600/133 Cel@600/66
FFmpeg H.264, s 546.3 409.5 221.1 369.9
FFmpeg MSMPEG-4, s 175.3 128.1 98.4 130.2
Theora, s 497.9 367.8 256.2 322.7

FFmpeg

FFmpeg was used for encoding MPEG4 to Theora/Vorbis.
The used version: ffmpeg-0.5_p20373
Command line:

time ffmpeg -i input_file.avi -vcodec libtheora -acodec libvorbis \
-vb 1024k -s 640:360 output_file.ogv

Input files: Big Buck Bunny, Sintel trailer.

movie OMAP@600 OMAP@850 P3@600/133 Cel@600/66
big buck bunny, m:s 143:21 102:38 43:45 47:51
sintel trailer, m:s 13:39 9:48 3:59 4:30

Compression

The used tools: bzip2-1.0.5-r1, gzip-1.4
Command lines:

time bzip2 big_buck_bunny_480p_stereo.avi
time gzip big_buck_bunny_480p_stereo.avi

Input files: big_buck_bunny_480p_stereo.avi

compressor OMAP@600 OMAP@850 P3@600/133 Cel@600/66
bzip2, m:s 6:48 5:17 6:08 7:45
gzip, m:s 1:55 1:39 0:53 1:42

Hashing

The used tools: coreutils-8.5
Command lines:

time md5 big_buck_bunny_480p_stereo.avi
time sha256 big_buck_bunny_480p_stereo.avi
time sha512 big_buck_bunny_480p_stereo.avi

Input files: big_buck_bunny_480p_stereo.avi

algorithm OMAP@600 OMAP@850 P3@600/133 Cel@600/66
md5, s 2.45 1.18 1.95 2.15
sha256, s 7.20 5.17 8.30 8.68
sha512, m:s 1:10 0:43 0:29 0:31

JavaScript

The used tools: midori-0.2.6, webkit-gtk-1.1.15.4, V8 version 5, SunSpider-0.9.

suite OMAP@600 OMAP@850 P3@600/133 Cel@600/66
V8 57.4 80.2 305 253
SunSpider, ms 23053.8 18327.0 4744.6 5520.4