Photoshop CS: Intermittent performance issues…

MM
Posted By
Martin_McNeil
Dec 30, 2003
Views
252
Replies
7
Status
Closed
I’m currently using PS 6 and am seriously considering taking an the upgrade route to CS Premium since I’m also currently using GoLive 5 and Acrobat 5; there seems to be both financial and features incentives that will benefit my work flow by upgrading at the reasonable price of £650 or so. I passed over an upgrade to PS 7 since I was waiting for the more feature-rich CS to appear.

I’m about 15 days into using the Photoshop CS trial and have darn near tore out my hair in frustration over the fact that it’s seemingly buggy and unresponsive in certain situations when compared to the trial version of PS 7 – or even to functions in PS 6.

I do a lot of work for the web that involves repurposing images taken on a 2.0MP digital camera – the file from the camera sizes are in the 250KB region, so we’re not talking major problems… but no matter what, CS slows to a crawl when working on them. FYI 75% of system memory is allocated to PS, and the pagefile is set at 1GB.

The heal and clone stamp tools are unresponsive, resizing and zooming takes forever and even brush strokes take an age to appear. The only way I’ve found to correct this behaviour is to immediatley save the image as a .psd file from the outset – but I don’t think this should be necessary.

My PC is of reasonable specifications and has never had issues running either PS 6 or PS 7 trial, and I fully expected it to cope adequatley with CS; specs will follow at the end of the post. I’ve even been considering moving to 2GB of PC3200 DDR and 2 x 74GB 10K rpm S-ATA drives to boost performance, but don’t want to shell out an additional £700 + if the issues are not directly related to hardware.

What I really need to know is how many of you out there are experiencing similar issues (it seems like quite a few from browsing the posts here) and if Adobe are tackling these problems. I don’t want to shell out £650 for the upgrade only to be hamstrung when I’ve got a lot of work on the go. I’m no newbie to either PS or PC’s since I’ve been using the former for four years and building the latter for six… but I’ll be damned if I can figure out what’s causing these problems.

Specs:
Windows XP Pro with all updates applied
Intel P4 2.4GHz / 533MHz FSB
MSI 848P Neo-LS Motherboard (Intel 848P Chipset)
2 x 512MB PC2700 DDR @ 333MHz
80GB 7200 RPM HDD with 8MB cache (System / Apps / Pagefile) P-Master 40GB 7200 RPM HDD with 2MB cache (Other Apps / Scratch Disk 1) P-Slave 20GB 5400 RPM FireWire HDD (Backup Drive / Scratch Disk 2) DVD ± RW/RAM Drive (Optical Backup) S-Master
16 x DVD Drive (Optical Media) S-Slave
1 x Zip750 USB 2.0 (Magnetic Backup)
nVidia GeForce FX5900 Ultra / 256MB, driver version 53.03 Onboard Realtek AC97 compliant audio
Onboard Realtek 10/100 NIC
Generic 3-Port FireWire PCI card
Wacom Intuos2 Platinum A5, driver 4.77-11

Master Retouching Hair

Learn how to rescue details, remove flyaways, add volume, and enhance the definition of hair in any photo. We break down every tool and technique in Photoshop to get picture-perfect hair, every time.

LH
Lawrence_Hudetz
Dec 30, 2003
Since you build PC’s take XP off and try the same system with W2K. It seems as if the only people having this kind of problem are running XP. Maybe I’m off base, but if it was me, I’d be giving it a try.

Another possibility: is the memory dual channel? That seems to be another commonality, except that the machine slows down with the addition of the second set of dual 512’s.
MM
Martin_McNeil
Dec 30, 2003
Firstly I build PC’s for myself, not commerically, and don’t have access to Windows 2000. As a freelancer I don’t have the luxury of either the time nor the finances to purchase a new OS and go about installing it just to run software that *should* work on my machine anyway…

Secondly, the 848P chipset doesn’t support dual channel memory – it’s a cut down version of the 865 chipset in that it supports DDR, HyperThreading processors and is Prescott ready but eschews things like S-ATA RAID (it still has two S-ATA channels) and Dual Channel DDR… so there’s no chance that Dual DDR is the cuplrit.

Besides, my main concern (and criticism) would be that if Photoshop CS is designed to work on a Windows PC, it should damn well do so without the need for hardware or software "tinkering" on the level that some people seem to suggest. If you have a PC that meets or exceeds the specifications to run Photoshop CS, then it *should* be able to run without such problems.

The mere fact that some people aren’t reporting these problems highlights the possiblity of bugs that need addressing. I know that the Adobe team can’t possibly test their software on every platform type and that patches and bugfixes are inevitable – but I’ve never seen Photoshop slow to such a crawl or simply stop responding when doing the simplest of tasks like working on a 5.5MB, 72dpi .jpeg – that’s a sure sign that something is wrong, don’t you think?
DM
dave_milbut
Dec 30, 2003
turn off background processing and high res thumbnail creation in the browser area of the prefrences. back the memory allocation down to about 45% and restart. inch it up from there til you find a happy medium.
RB
Robbie_Boyer
Dec 30, 2003
I run on a windows 2000 machine with 1.5 gig of ram. I have turned off high res thumbnails and have background processing off.

I still find that Photoshop pulls some major slow downs compared to 7. It’s not just you.
DM
dave_milbut
Dec 30, 2003
did you turn down the memory allocation in prefs? you can also try bumping the cache levels up to 6. you need to exit and restart photoshop after all of these changes.
RB
Robbie_Boyer
Dec 30, 2003
Yes I tried both of those and yes i restarted Photoshop but still found it to be unresponsive at times.
LH
Lawrence_Hudetz
Dec 30, 2003
The suggestion to try W2K is out there for anyone else to try also, and some people have multiple boot capability.

So far, with a relatively ancient box (Asus A7 Pro, Athlon 850, 1 G Ram, W2K) the big slow down is when I am in 16 bit with a number of layers and 2 or more filters. The biggest slow down is the final step in Save. I am running Scratch at 80%, and just yesterday returned to hi res thumbnails to see if there is any additional slowdowns. It’s obscene to me that one has to start at 45% allocation when installing additional ram.
There is an additional process change I have noticed which may prompt people to say it’s slow. In PS 6, when I choose levels for instance, the histogram shows up quickly, and after making adjustments, the time lapse when accepting the change was noticable. Now, I wait longer to initialize, but OK is instantaneous.

There is a lot of changes like that to get used to. Another is using the Eraser in Quick Mask and other processes where I used to use Brush. It has the effect of inverting the Background/Foreground selection to add or subtract from the mask. That slowed ME down for a while! 😉

Do the G5 systems also see this slow down?

MacBook Pro 16” Mockups 🔥

– in 4 materials (clay versions included)

– 12 scenes

– 48 MacBook Pro 16″ mockups

– 6000 x 4500 px

Related Discussion Topics

Nice and short text about related topics in discussion sections