Zardon

No, then hard drive comes into play. something intentionally avoided in this test and noted on the photoshop page information text. If i had wanted to incorporate the hard drive into this performance test the image would have also been larger to use the PS scratch disk but this will cloud the results the test is aimed at - CPU, Memory/bandwidth etc

Judas

oh ok. Been awhile since i read though everything on there since it was first posted, was checking out a few machines that i had ran it on and wonder if perhaps the preformance messurement would include HD at all...

understand now.

__________________

ocztony

Hey guys i just wanted to show what the new Conroe is like at the DH bench for CS2, seem you have a new leader at the top

This with a 2.16 overclocked to 3143mhz all on air.

Zardon

yeah they pretty much smoke everything else........

swimtech

...and a Macbook Pro running Windows ties a Dual 2.5Ghz G5 PowerMac running OSX.

__________________
It's not so much getting your way that matters or not - what matters is how you go about getting it.

tastyweat

Hehe... first run with new processor and I get 9th on the leaderboard with 110.3 seconds

Happy

__________________

tastyweat

Fresh Restart and I jumped to 8th with 106 seconds.... 0.5s off 7th place!!! lol

__________________

Wwhat

After getting the test and musing on the results a bit I found a way to significantly improve them, I realised that PS keeps a history, and with the huge alterations done the historybuffer gets really big, so I went to options and changed history from its default 20 to 1 and here's some of the differences:

test - was - became
5 - 20.6 - 16.2
6 - 4.7 - 1.6
7 - 10.4 - 6.7
9 - 19.1 - 14.4
12 - 32.1 - 21.4


So there you have it, sloppy of you guys to not realise the history would hugely influence this test.

Go ahead and try it yourself and post the differences.

Zardon

Nothing sloppy about it and your findings are hardly groundbreaking, there are loads of ways to get increased scores and to optimise a particular system, this isnt 3dmark via the orb type testing - this is a real world test, thats why I said in the instruction to run the bench on a fresh load. There are even huge differences between versions of photoshop and the code changes they make.

pr0digal jenius

yea, and in real life you would likely much rather have those extra undo steps then a few seconds render time

Wwhat

You make a benchmark, you make a page on which you specify versions of PS etc.
You also make a database of results people get, yet you ignore an obvious influencing factor that can skew the results by 30%. and you call that not sloppy
There is only one conclusion, you are afraid to admit you did something daft.
Perhaps you can get a job at the government or army then eh.

How about a simple 'Oops, silly we didn't think of that, we'll add it to the instructionspage' instead of this nonsense huh.

tastyweat

If you had bothered to read the instructions page then you would have seen that it's already there.

If you're going to accuse people of negligence... make sure you get your facts straight in the first place.

__________________

Zardon

Hi again, no offense here but I think it is time for a bit of education on the subject.

Firstly I didn't "make" a benchmark, you like some are under the impression that this is a futuremark style test. There are many differences so I feel it is best to perhaps explain why people like yourself are interpreting key issues incorrectly.

The DH Photoshop benchmark is basically a set of instructions gathered together into an action"script" which runs and displays the time to perform these functions. These are all already built into the program, I have coded nothing nor am I using any influential third party addons. Everyone can run these, even macintosh users.

Now that is clear let me explain further. A program like futuremark's 3dmark is a synthetic application built by in house coders to test specific functions under strictly controlled userbase environments. Futuremark do not let you open up their code and start optimising it for your specific hardware configuration as it defeats the purpose of that specific application - you can do nothing with 3dmark except run a predefined set of parameters.

Adobe Photoshop is a real world professional graphics application that allows the end user with knowledge the opportunity to adapt, optimise and increase performance for a specific task or hardware/software configuration. Equally in the wrong hands these tweaks could cause huge issues depending on ram, hard drive size, speed and other key factors. This is why Adobe with each version of Photoshop have a preset and safe installation configuration which will work in the majority of end user scenarios. This ensures the program will run well under all conditions (as long as the hardware in question meets the application minimum requirements).

Between each version of Photoshop from 4 right through to 7, CS (8) and CS2 (9) adobe have the benefit of years of code optimisations to increase performance, this renders comparisons of a user running the benchmark with the same hardware configuration on V7 then CS2 (for example) incomparible. Version 9 (CS2) has some major code overhauls and users with quad chips or for example the intel 965EE with 2 core and 2HT see huge gains with specific filters that make requests to all the threads.

It is therefore with some common sense that we already know, comparing scores between versions is impossible, but we also know that for an experienced end user to tweak configurations between benchmarks that he is going to notice changes, this is a part of the benchmark's usefulness. Not only can a user go online to our database and find another user with a similar system to compare against but he can also tweak his own system, either in the bios or in the program itself to see gains, depending on the amount of ram installed, the speed. the stratch discs and whether it is running on an OS drive, a raid partition, a 15,000 SCSI drive.

The benchmark has a myriad of uses on many levels, but it certainly is not intended to be an online comparision directly between users running different versions of the program with perhaps 2 gigahertz differentials in processor speed and those who have tweaked the program to the hilt for their own specific configuration. Perhaps I could write a guide on how to optimise the program for a variety of end user, however our benchmark page is not the place, and hopefully i've explained why.

likewhoa

anybody know why http://www.driverheaven.net/photoshop gets redirected to http://www.driverheaven.net instead? I'm trying to download the benchmark tool. I was able to dig the direct link which is located at http://www.driverheaven.net/photoshop/dhpsbench2.zip
eitherway, link should be looked at.

woodinville dave

Thanks for the link, I was having the same issue. Do you know the link to the instructions? I've managed to figure out how to run the action but I can't find the timing window. I'm trying to test CS3 with the action.