- Joined
- Feb 19, 2011
- Messages
- 421
Hi,
I noticed that my Geekbench scores went down over time and did not know why. The more I tested the more they went down. I tested by killing all processes etc having a mostly bare OS X etc.
Today I tested it WHILE running Ableton Live 8.2 Suite, a Pro audio application (DAW).
What I found were ... wow NICE Geekbench score? I even had 3GB samples loaded... I wondered WTF... why? So I went on and quit live and re-ran the benchmark. Lots lower score again... switched on Live again... higher score.
=> Geekbench is utter crap. Stay away from it. Useless. Its useless to measure anything. We have to find something else (like Prime maybe? Quake3 (there are some Open Source ports), NovaBench (seems pretty reliable)... Cinebench works awesomely for testing imho.
Here are 3 takes of Geekbench running while Ableton Live runs.
Here are 3 takes of Geekbench running without Ableton Live running.
p.s.: You could say it is OS X's fault, I will test this later on my MBP. If its the same its not OS X fault. Its a standard OS X on a standard MAC => Geekbench's fault then.
I noticed that my Geekbench scores went down over time and did not know why. The more I tested the more they went down. I tested by killing all processes etc having a mostly bare OS X etc.
Today I tested it WHILE running Ableton Live 8.2 Suite, a Pro audio application (DAW).
What I found were ... wow NICE Geekbench score? I even had 3GB samples loaded... I wondered WTF... why? So I went on and quit live and re-ran the benchmark. Lots lower score again... switched on Live again... higher score.
=> Geekbench is utter crap. Stay away from it. Useless. Its useless to measure anything. We have to find something else (like Prime maybe? Quake3 (there are some Open Source ports), NovaBench (seems pretty reliable)... Cinebench works awesomely for testing imho.
Here are 3 takes of Geekbench running while Ableton Live runs.
Here are 3 takes of Geekbench running without Ableton Live running.
p.s.: You could say it is OS X's fault, I will test this later on my MBP. If its the same its not OS X fault. Its a standard OS X on a standard MAC => Geekbench's fault then.