18 seconds
Octo 2.8 OC'd to 3185 with 8 GB memory and 2X WD Raptor on RAID0 as Boot/Scratch.
(It took 20 seconds at first, then I did it again without restarting Photoshop, I don't know if that's cheating though.)
10 rupees says the new Nahalem Mac Pro's don't do this test as fast as a Nahalem PC for 1/3rd the price.
Well, I think Nehalem Xeons and Nehalem i7s at the same clock will perform the same in this particular test. I don't see any reason to think that a 2009 quad core Mac Pro at 2.66GHz or 2.93GHz will perform this test any slower than an i7 PC at the same clocks respectively. Of course, the i7 PC will cost considerably less. So, the Mac would be performing the same as a PC that might cost 1/3 less.
Now, if you overclock that i7 PC, it'll perform significantly better than the Apple offerings without costing any more. In that sense, a quad 2009 Mac Pro won't do the test as fast as a Nehalem PC. And that'll be just as true once DP motherboards are released. Although, I think if this test has shown us anything, it's that Photoshop isn't using more than 4 cores. Evidenced by the fact that lots of people's 4-core Hacks and Macs perform the same or better than other people 8-core Hacks and Macs.
So, if Photoshop is your thing, you won't get any benefit in that application with more than 4 cores. Now if you want to run Photoshop while encoding something or while running another processor intensive application then you might have a good reason for going for a DP 8-core setup.
the slower buffered memory in the Mac Pro meant the Quad PC's could consistently pull faster results.
Maybe there's a small difference at the same clocks due to faster memory, but I don't ever recall any benchmarks that indicated that, at the same clocks, the faster memory of a Hack was making that much of a difference. I'm specifically thinking of Geekbench and Cinebench.
Edit:
Check out these Geekbench results.
Hack Quad 2.66GHz
Mac Quad 2.66GHz
And awulf's Cinebench results pretty much tell the same story.
Cinebench
Hack Quad 2.66GHz: 1CPU = 3480; 4CPU = 14825
Mac Quad 2.66GHz: 1CPU = 3573; 4CPU = 14753
So, even though, in both cases, the Hack is using faster memory, the machines perform almost identically at the same clocks. That isn't to say that there are no situations in which the faster RAM might pay off more than what's being shown here.
Sorry should have been more clear, I'm was talking about the benchmark this topic was created for, The Retouch Artists one.. If you scan back over the pages most of the Quad PC's were pulling circa 18sec times with the 2.8 Octos coming in around 22. It's not LOADS faster, but I just said it would be faster, which I still think it will be. I think this topic has become a little lost with all the different benchmarks being thrown into it!
The Cinebench results are quite amusing though!
The Cinebench results are quite amusing though!
I see. Are the 18 second results your talking about on machines running at 2.8GHz? I know I posted some 18 second results with my Hack quad but mine is running at 3.7GHz; almost a full GHz higher. Maybe I'll downclock my system to 2.8GHz and 800MHz on the RAM to see how it compares to the average 2.8GHz Pro.
Yeah, a OC'd 4-core i7 performs better in Cinebench than a 2.26GHz 8-core machine. That's impressive, even if a bit unsurprising.
What do you get on your Hack out of interest?
The last result I posted in this thread was 18.8 seconds at history 1, cache 4, memory 100% at 3.7GHz.
Very interesting.. Reconfirms my desicion to stay with my Q6600 setup untill i7 has matured a little, doesn't seem like I would gain much real world performance moving. Good job, I was beggining to get a little tempted!
It seems 17/18seconds is about the floor limit for this test, I wonder why?
Cinebench
Hack Quad 2.66GHz: 1CPU = 3480; 4CPU = 14825
Mac Quad 2.66GHz: 1CPU = 3573; 4CPU = 14753
So, even though, in both cases, the Hack is using faster memory, the machines perform almost identically at the same clocks. That isn't to say that there are no situations in which the faster RAM might pay off more than what's being shown here. I just have yet to see something that indicates that the faster RAM makes as big a different as you're suggesting.
2009 Mac Pro 2 x 2.26GHz Quad, 16GB 1066MHz DDR3, ATI Radeon HD 4870
22 sec
Same result from the same basic machine equipped with 12GB and the Nvidia GT120. I didn't expect the different graphic card to have any effect on the result and I wanted to confirm that. I wasn't disappointed.
Just checking it out : did adobe promise some improvement to the performance with the gpu´s in CS4 vs. CS 3?
Remember some talk about it but havent seen any hard evidence.
Just curious.
Adobe has just been so full of ***** the last few years with the PS performance it is starting to be hillarous.
If I wouldnt be working with it daily,that is..
Out of kicks, decided to humor everyone including myself, and realized that 22seconds seems to be the max. 18seconds if you reload the image and run the test again. I used a Mac Pro (2009) 2.93 8 core, 12gb ram, Photoshop CS4, with no other apps, at the settings requested. Repeated the test and each time from scratch got 22 seconds. Hope this helps, but seems this test is useless for the newer machines.
Peace,
Noushy
Lets see what it can do when Adobe releases CS5 running 64bit native. I heard that is going to be timed with the release of snow leopard.
Where did you hear that? Usually Photoshop is on an 18 month development cycle which should place the next release between March and June of next year.
Jim
Uuh,duude..
It is from april 2008,and the "next" version they refer to is CS4..
So the über performance they rave about can be seen at works in CS4...hehhe..
.
So,it is just about to sit back and wait for the CS5 that is propably arriving in agust 2010. Maybe then again we will se whopping 5% boost in speed again.
OR,adobe might manage to engage a second core!!! That would double the performance of the photoshop!!! Imagine that!
http://blogs.adobe.com/jnack/2008/04/photoshop_lr_64.html said:(Our goal is to ship a 64-bit Mac version with Photoshop CS5, but we’ll be better able to assess that goal as we get farther along in the development process.)