Ok, I am sad.
Today I noticed a new version of Geekbench, 2.2.0
It has important changes, interface, hardware detection methods, and most probably, how the benchmark routines are executed.
I am using for the first time a VPS with the new OpenVZ memory scheme, and tried to execute Geekbench 2.2
I got this http://browse.geekbench.ca/geekbench2/view/478211
In summary, bad hardware detection, low scores in the memory subsystems and a very slow execution.
Maybe caused for the new OpenVZ, or an slow node?
I scp'd my old Geekbench 2.1.13 to this VPS and executed.
Got this: http://browse.geekbench.ca/geekbench2/view/478222
Better detection, faster execution and better scores in the memory sections. But the final score is similar.
I tried to do the comparative in a VPS (192MB Debian Squeeze) with the old OpenVZ (RHEL5), and got this trying to execute Geekbench 2.2
Geekbench encountered an internal error and cannot continue. Please contact [email protected] for assistance. Internal error message: std::bad_alloc.
Seems that it uses more RAM and can't finalize (I was using just 21MB of that 192MB).
Also, tried in a VPS with Debian Lenny and 300MB free:
./dist/Geekbench-2.2.0-Linux/geekbench_x86_32: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by ./dist/Geekbench-2.2.0-Linux/geekbench_x86_32) ./dist/Geekbench-2.2.0-Linux/geekbench_x86_32: /lib/libc.so.6: version `GLIBC_2.11' not found (required by ./dist/Geekbench-2.2.0-Linux/geekbench_x86_32)
Then, I tried in a VMware VPS, a KVM VPS and a Rackspace 1024 MB (Xen, it seems):
Run Geekbench as root to gather accurate system information. Floating point exception
With root just crash without messages.
Finally, I tried in a physical machine with 4GB RAM and Debian unstable:
Better scores for the 2.2 in the CPU sections and aproximately the same for the Memory sections.
Also, noticed with htop that this new version needs around 400MB RAM to be executed while the 2.1 needs 50-100MB (I am not sure because is executed very fast lol). And that is probably the reason because my RHEL6 vps got low memory scores, lack of RAM.
In brief, Geekbench 2.2 is performing like CRAP in virtualized environments
- Uses excessive memory, I wasn't able to finalize a test in any of my VZ containers for the lack of RAM.
- Not accurate hardware detection in the new RHEL6 OpenVZ
- In RHEL5 sometimes runs, sometimes doesn't.
- In Xen (Ubuntu 11.04), KVM (Whezzy), VMware (Whezzy) doesn't run.
So, I can't recommend this new crap for benchmarking our LEBs. I advise to grab a copy of 2.1 and store it like a treasure xD
Sad day to me u_u