CINEBENCH is the free benchmarking tool for Windows and Mac OS based on the powerful 3D software CINEMA 4D. Consequently, the results of tests conducted using CINEBENCH 10 carry significant weight when analyzing a computer’s performance in everyday use. Especially a system’s CPU and the OpenGL capabilities of its graphics card are put through their paces (even multiprocessor systems with up to 16 dedicated CPUs or processor cores). The test procedure consists of two main components; the first test sequence is dedicated to the computer’s main processor. A 3D scene file is used to render a photo realistic image. The scene makes use of various CPU-intensive features such as reflection, ambient occlusion, area lights and procedural shaders. In the first run, the benchmark only uses one CPU (or CPU core), to ascertain a reference value. On machines that have multiple CPUs or CPU cores, and also on those who simulate multiple CPUs (via HyperThreading or similar technologies), MAXON CINEBENCH will run a second test using all available CPU power. Again, higher Frames/Second and lower rendering time in seconds equal better performance.
Since the Intel Atom N270 processor has Hyper-Threading (HT) technology, we ran the multi-threaded CPU test on Cinebench R10. We obviously don’t expect much in terms of performance from this low-power consuming CPU that makes this netbook a netbook! However, it took almost 14 minutes to render the image!
wPrime uses a recursive call of Newton’s method for estimating functions, with f(x)=x2-k, where k is the number we’re sqrting, until Sgn(f(x)/f'(x)) does not equal that of the previous iteration, starting with an estimation of k/2. It then uses an iterative calling of the estimation method a set amount of times to increase the accuracy of the results. It then confirms that n(k)2=k to ensure the calculation was correct. It repeats this for all numbers from 1 to the requested maximum.
wPrime is also a multi-threaded synthetic benchmark used to time how long it takes to calculate the square-root of a number. This benchmark took just over 2 minutes to run the 32M test.