I have read of severel posts that CS is very slow compared to 7.
Have you read the ones that say that it isn’t?
Bob
Bob
Yes I have read those and I was hoping that this thread would consildate some of the opinions and If Scott or any other Adobe person could comment on this it would be appreciated.
Thanks again
Julio
Most of the "slow" speed posts were related to either win 2k (you have xp, so you should be ok) or related to the file browser when creating thumbnails. In the browser case, most people have reported speed back to near normal (ps7) after the thumbnails are created.
I find it runs as good as or better than 7 on my 2.8 p4, 1 gig ram.
It takes me 7 minutes to boot up Photoshop CS whereas Photoshop 7 only took about a minute and a half..nothing changed, just the version. I am using Windows XP Pro with 1 GB Ram and proper scratch disk configuration.
It IS slow for me.
Sweet-P
wrote in message
Most of the "slow" speed posts were related to either win 2k (you have xp,
so you should be ok) or related to the file browser when creating thumbnails. In the browser case, most people have reported speed back to near normal (ps7) after the thumbnails are created.
I find it runs as good as or better than 7 on my 2.8 p4, 1 gig ram.
I don’t know if it has been stated anywhere, but I’m curious if PS CS is has better performance on a P4 system relative to PS7 while possibly worse performance on a P3 system. That is, could it be that PS CS is optimum for a P4 but PS7 is optimum for a P3? I need to rerun some tests since I’m not certain all the thumbnailing had been completed, but my impression for my Dual 550MHz P3 system is that PS CS is noticeably slower performing than PS7.
Regards,
Daryl
You can uncheck "Allow Background Processing" in Preferences>File Browser. It’s really fast now :))
Well I didn’t measure it definitively but my gut feeling having just upgraded to CS is that it’s about the same – that’s on a 2.0GHz 512Mz P4 machine, 512Mb ram running XP Pro. I expect if I do everything in 16 bit mode then it will slow down but like for like no obvious difference.
Cheers .. Keith
well mine definetly slows down when working with images and multi layers.. all the things that wiz right through with ps 7.01 on the same computer.
I am possible going to upgrade my 512 meg ram to 750 or 1 meg to see if it will help??
I have a P4 1.7Ghz with 512MB RAM and 220 combined HD storage space and I noticed a great decrease in the speed of tasks in CS compaired to previous versions of PS and I am using Win XP home. I have seen many other posts with the same complaint, so I think it should be adresssed by Adobe soon.
So, lets see if I can provide some clarification:
We haven’t seen a systemic slowdown. We’ve seen a slowdown on some machines, for a couple of different reasons, and most could easily be solved and/or explained. We’ve seen only one thing which indicates a real problem, and only on 16-bit deep images.
The File Browser preferences come with Generate High Quality Previews on by default. That means that after fetching thumbnails and metadata for files, the File Browser will then generate a big preview. This is new, and takes a big chunk of processing time, so if the File Browser is open, the whole app will seem slow until that process is complete. There are also some new file types the File Browser can generate previews for, so that adds to the apparent slow down. Closing the File Browser or unchecking that Preference generally solves this issue.
A couple of routines are slower – some for quality improvements that we felt was worth the tradeoff (resampling, for example) and some for bug fixes (a number of the Gallery Effects filters).
Daryl guessed well – we did change the optimization options slightly, because we didn’t see enough of a slowdown on older systems for it to be an issue. And note that this ONLY affects the UI code, not the computational code, so that the most intense operations aren’t affected at all. Note that the File Browser isn’t appropriate for speed tests because it was rebalanced for better UI responsiveness and it handles more file types.
I have started to see a pattern with 512MB machines that suggests the default Photoshop CS memory percentage may be too high for some folks. Some very memory hungry processes (MP3 players and Instant Messaging) are much more common, and the system may run out of RAM more often now. The executable is larger with the new features added, and it could be enough to push some things over the edge. Use Task Manager on the Performance tab to watch Available Memory and if it falls below 15000 (15MB) it’s time to back off Photoshop’s Memory Pecentage a bit (do it in 5% increments). We should have accounted for the additional executable size in the memory calculations, but didn’t (sorry!).
We fixed a bug in our printer handling from 7, but it means we try and check the printer settings more often. If you have a network printer that has been disconnected or is otherwise unavailable, this *may* result in unusual pauses at launch (before the splash comes up) and when creating a new document or opening a file (I say may, because it’s not clear exactly what state the printer has to be in to cause the issue). Selecting a local printer or a different printer as the default printer solves this issue.
I’ve also seen indications that the number of cache levels is, by default (4), a little low. Try 5 or 6.
So, "Is CS Slow"? No. But there are things to be aware of, and things we’re watching to see if there is something we haven’t seen yet.
-Scott
Thank you Scott.
A great explaination.
Julio
Scott,
If you increase the cache level to anything beyond "4" PS CS won’t even open documents. But thanks for the suggestion.
Just bumped it to 6, seems fine here.
Steve – it shouldn’t cause problems like that. We tested it on all the allowable levels….
Daryl,
I have a dual 866 MHz P3 and 2 GB RAM (WinXP Pro SP1).
The only significant slow down I have experienced, is when I create a new document. The ‘New’ dialog box seems to "fade in". First I see the box itself and later the numbers appears like this:
<
http://home18.inet.tele.dk/madsen/photoshop/cs/new_document. gif>. In PS7 I see the ‘New’ dialog box and can use it the same second I choose to make a new document.
I see the same thing in both Illustrator CS and InDesign CS. They’re all significantly slower to show me the ‘New’ dialog box than their predecessors.
Another thing:
In PS CS I just see an hour glass the first two to three seconds after the splash screen has gone, if I click on the file menu or any other menu. In PS 7 the program is ready when the splash screen disappears. Not that I can’t wait those few extra seconds of course. It just takes a while to get used to. When PS CS is up and running, I find it almost identical (in performance) to PS 7.01.
—
Regards
Madsen.
In PS CS I just see an hour glass the first two to three seconds after the splash screen has gone, if I click on the file menu or any other menu.
I’ve noticed that too. It’s like something’s not quite done initializing. Takes, as you say, just a couple seconds then everything’s ready to go. (the "Welcome" screen is turned off in my case).
Hi again,
I forgot to mention that the File Info dialog box doesn’t look very good in PS CS. All the letters are cut off like this:
<
http://home18.inet.tele.dk/madsen/photoshop/cs/file_info.png>.
It’s because I’m using ‘Large size (120 dpi)’ instead of ‘Normal size (96 dpi)’ inside Control Panel > Display > Settings > Advanced > General, but shouldn’t Photoshop compensate for that? Photoshop 7 doesn’t seem to have any problems with the ‘Large size (120 dpi)’ setting (Photoshop 6 had).
—
Regards
Madsen.
wrote:
(the "Welcome" screen is turned off in my case).
In my case too.
—
Regards
Madsen.
Thomas – yes, that is because of the large fonts.
Chris,
I thought so. ‘Normal size (96 dpi)’ is just to darn small in my opinion. It’s fine for monitors running in 1024 x 768, 1152 x 864 or even 1280 x 960, but not for monitors running 1600 x 1200 and beyond. I want too be able to see things clearly from a distance of about 40 inches to the monitor. I definitely don’t want to end up like this: <
http://www.funkypages.com/evolution/evol.jpg> 🙂
—
Regards
Madsen.
Well, that’s because your display is supposed to be between 72 and 96 dpi. Trying to cram 1600×1200 into a 17" CRT just doesn’t cut it 😉
Yeah, we know about the font problems. We’re looking into it.
wrote:
Yeah, we know about the font problems. We’re looking into it.
Okelydokely 🙂
—
Regards
Madsen.
I’ve got a 3.0GHz Hyperthreaded Intel Pentium 4 CPU overclocked to 3.3GHz, with 1GB of Dual Channel RAM and two Western Digital Raptor 10,000RPM drives RAID-0 SATA (190MB/s).
It runs fast ;D
…. Sorry, I have no real friends that would care about such gloating. I needed to get that out ;D
overclocked
let me know when your cpu melts.
wrote:
I’ve got a 3.0GHz Hyperthreaded Intel Pentium 4 CPU overclocked to
3.3GHz, with 1GB of Dual Channel RAM and two Western Digital
Raptor 10,000RPM drives RAID-0 SATA (190MB/s).
Smartass 🙂
—
Regards
Madsen.
Chris, I know it shouldn’t do that, but anything above a cache level of "4" and PS CS won’t open documents.
As for me it’s much faster then previous version! Even in 300dpi working with real a4 or a3:) When creating Gry Java Nokia Siemens Motorola <
http://www.logosik.pl/> site, i was amuzed and surprised it’s so fast… as for me:) Using Amd Athlon XP 1800+ Radeon 9800 pro (gigabyte) and got 1mb of HyperX Kingstons (512×2 2.2.2.5.2 settings) + 2xWD80GB(JB) 7200 RPM 8mb of cash:)
The only significant slow down I have experienced, is when I create a new document.
That’s an OS dialog, I suspect XP is just having a little issue on your box. Nothing to worry about if you can live with it :-).
Another thing:
In PS CS I just see an hour glass the first two to three seconds after the splash screen has gone, if I click on the file menu or any other menu.
It’s building the "How To" help menu items in the background. On a faster machine, this really does end up being "background", but I think on your machine it’s taking up enough of the available CPU to be, uh, noticable.
-Scott
That’s an OS dialog, I suspect XP is just having a little issue on your box. Nothing to worry about if you can live with it :-).
I can live with it.
It’s building the "How To" help menu items in the background. On a faster machine, this really does end up being "background", but I think on your machine it’s taking up enough of the available CPU to be, uh, noticable.
Well, I just have to buy a faster machine then… 🙂
—
Regards
Madsen.
On a faster machine, this really does end up being "background", but I think on your machine it’s taking up enough of the available CPU to be, uh, noticable.
2.8 p4 hyperthreaded, intel d865perl mobo w/800 mhz fsb, 1 gig pc3200 400mhz ddr ram (2 – 512’s), serial ata 160 g hd. 8x agp ati aiw 9700 pro. not fast enough? 🙂
"let me know when your cpu melts."
I’ve got adequate cooling. Really, I can’t tell a difference between 3.0 GHz and 3.3 GHz. But since I have the ability to do it safely, might as well.
Dave,
2.8 p4 hyperthreaded, intel d865perl mobo w/800 mhz fsb, 1 gig pc3200 400mhz ddr ram (2 – 512’s), serial ata 160 g hd. 8x agp ati aiw 9700 pro. not fast enough? 🙂
It can’t get much faster than that, can it? 🙂
(Sure it can but nevertheless, I would call your computer for a really fast one).
—
Regards
Madsen.
maybe scott was talking about a dualie G5 when he said "fast computer". 🙂
Hi
Need to jump in here. I upgraded to CS and have to confirm the slowness. First i thought it is the new graphics card (matrox parhelia 128). So i switched back to my old one. Same result. Now i re-installed PS 7 and both graphic cards are just jamming.
So here is what happens.
Using CS, i can paint for a (short) while, then it starts to lag and i hear that the pc is starting to swap on the disks. My taskmanager still tells me 600 Mb (out of 2gig) available.
Anyway, it gets worse and worse the longer i work in CS. Zooming in or out makes the screen go white and i can watch how PS slowly rebuilds the screen. (that’s why i originally thought that i have a problem with my graphics card)
So i went back to PS 7, paint on the same image without any lag, without any problem. Zoom in and out at will.
here’s some specs:
amd 2000+
abit kra7 raid mobo
lots of disks
2gig of RAM
wildcat vp870 (matrox parhelia 128) am running two monitors.
Now that i have tried all 4 combinations between PS 7 and PS CS with the two graphic cards i have to say that at least here on my setup Phostshop CS is so slow that i can’t use it.
just wanted to let you know.
momo
what operationg system momo. there have been reports of probs with win2k. and there’s a thread to that effect somewhere. mostly seems related to networking or network printers (at least that’s what I get so far.) also the new browser can slow things down when it’s first creating thumbnails. turn off background processing and high quality thumbs in prefrences and see if that helps.
one more thing momo, try turning down the memory percentage to below 70%…
I signed up here because of the slow performance. I was hoping to find a fix for it but it looks like we’re all in the same boat until a patch comes out?
I have another question that fits this topic though. Are there any troubles in CS caused by video drivers? I’ve had aberrations when applying effects/textures on large images that I’ve not seen before. For instance, the image itself will turn to the page background color and stay that way until the filter or texture is applied, then it will flicker for a few moments before re-appearing. ? Maybe just part of the slowness deal?
the flicker sounds like a video driver problems tempus.
as for the slowness, did you try any of the fixes suggested here and in other threads? turn off high quality thumbs and background processing. turn down the mem usage. if you have a network printer, set a local printer as default, etc.
what os, hardware, etc. info please!
Yep, I turned everything down yet it still bogs down. I watched in task manager and it seems to be maxing the processor, not memory. I’ve done this with older versions and never maxed out the processor on such small images (all under 3 megs). I haven’t been using the built in file browser yet either, still using ACDSEE 5 for that.
Oh yeah, it’s a 2.2 P4 768 megs RdRam. WinXP homely edition, dual monitors running (doesn’t seem to change when I shut one off), GeForce 128meg TI4600, and most background tasks turned off. I’ll load up new video drivers later on and see if it helps with the flicker.
Thank’s for looking into these things, it’s really nice to have someone there…and on a Saturday? I really didn’t anticipate any feedback ’till monday. Thank’s again.
this is a user to user forum tempus. i’m just sitting here smoking, taking a break from watching monty python and the holy grail! (silly k-niggits!)
still many of the adobe people have been around with the new release (in an unofficial capacity) and this is an issue they’re very interested in resolving. i just passed on a few things and asked for the info they’re going to need to try to resolve it.
did you check the prefrences for the file browser anyway? there’s a background process option and high quality thumbnail option. so even if you haven’t opened it yet, it still might be creating thumbnails in the background. look in Edit> prefrences> File Browser.
thanks dave
I am running XP pro, service pack 1, i forgot to mention. As far as network goes. I firewalled photoshops attempt to connect to its server (or wherever) everytime i open CS. Can that be related to that??
I noticed that something tries to connect the network in the moments when CS finally freezes. Anyway, i turned of the background processing and it seems to help a little bit. But it still lags and freezes when painting.
I can take a 150pixel brush in PS 7 and paint without lag on a 4000×4000 pixel image. In CS i can make 4 strokes and then have to wait for a few seconds, then after another few strokes CS freezes for 10-20 seconds,and so forth. and the lag gets longer and longer the more i paint.
I do not have any of that in PS 7.01.
momo
After some days of work with CS I also have to add here that it sometimes is amazingly and irrationally slow. Particularly in refreshing the image content after small operations like moving a layer around. I make a move of the layer with the move toll and pS temporally comes to a halt of about 7 – 10 seconds before displaying the new position.
I’m not even talking abut very large files.
The problem is , there doesn’t seem to be any pattern this lag follows. sometimes it happens and sometimes not.. during one session.
I made sure there’s is nothing running on the background except for the absolute required Windows XP services.
Like someone else I also noticed , its not low memory lag, but heavy cpu usage. In Ps7 the same operations on the same file are simply swift.
the basics of my system are :
Windows XP pro with sp1 and all other updates.
Asus A7n8x Deluxe ( revision 2.0 ) Nforce2 chipset with latest drivers. Athlon XP 2800 + ( barton) I gigabyte of Ram ( Corsair 400mhz) Ati Radeon 9700 pro ( catalyst 3.9 drivers) with dual monitor setup ( one 22′ Mitsubishi and one Hitachi 19′)
I firewalled photoshops attempt to connect to its server (or wherever) everytime i open CS. Can that be related to that??
it might. as it’s just trying to connect to localhost, it’s not really a problem. do you have any network printers assigned? as default maybe? if so switch to a local printer as default (even if one doesn’t exist).
I am hoping to seek a solution here for the slow PS CS i had encountered but seems to no valid. = (
Before installing Adobe CS, i was using the old version of Photoshop. Everything was pretty fast. But after installing Adobe CS, its slowing down my system (P4, Window Professional XP) every single action i applied in Photoshop 8.0 seems to take ages and definitely slowing my work process and sometime even hang my system. Kinda of frustrating, despite switching off the the necessary File Browser preferences..
Hopefully, solution comes fast!
Hopefully, solution comes fast!
Well, we can’t solve what we can’t reproduce. So, please, try the other suggestions (pulling down Photoshop’s memory percentage slightly, making sure cache levels is at 6 or higher, etc.)
Also note that the tile size for Photoshop’s scratch was increased for Photoshop CS, so that it may take longer for the first display update to occur when working on larger files, but overall working time will be lower.
-Scott
It seems that not everybody has that problem with a slow CS. I was wondering if this topic just fades out or if there are any news or maybe solutions to this. Because as much as i would like to use CS, i can’t, it is effectively unusable for me. (i am using ps mostly for painting)
Are there any known issues with amd processors? with the via chipset, with certain motherboards??? What can i do now besides going back to ps7 ?
momo
here’s again my data:
amd xp2000+
abit kra7 raid
2gig of ddr2100 memory
3dlabs VP870
wacom
lots of diskspace
momo – have you tried the existing suggestions?
And are you running Win2K or XP?
Hi Chris
Yes, i think i tried everything i can think of.
Lowering the max memory usage, increasing the cache levels (up to 8) . I disabled the background processing and turned high quality previews off for the browser. I closed the histogram window, as i noticed that this constantly calculates when it is open, and therefore slows things down a bit. (does it still calculate even when it is closed???)
There is no network printer listed, but my local one, which is correct. I tried it with one display and with two displays, with matrox and with 3dlabs graphic cards, i also upgraded every driver i am aware of.
I tried several combinations of my harddisks for scratch disks. I also swapped memory banks. (it’s a long holiday weekend here)
But it always has the same result, i can paint for a few brush strokes, then CS starts to lag, when i continue to paint CS starts to freeze for a few moments.
The cpu doesn’t do much, the installed 2gigs of ram are not even remotely utilized. All i hear is the harddrives and the display rebuilds itself very very slowly.
This goes on until i just can’t work anymore. Clearly CS (or the memory) tries to cache here something, or can’t keep up with the dataflow. (ok, i am not a techie) But it is not using much of the available memory.
I must have something in my PC that bites CS. But i don’t know anymore what else i can try to find out what it actually is. Maybe it is some driver issue? But if which one?
It works flawlessly with PS 7.01, its fast, instant, i can paint on really big images (4000 x 4000) without any problem. No lag at all, and i tried to paint with a big brush very fast, and as soon as it does lag, it easyly catches up again. No freezing at all. perfect. i think i have a really fast setup here.
btw. i am running XP pro version 2002, service pack 1 and lots of security updates.
momo
I just went back to PS701 and only use CS when I want its new features. I’ll just wait till the patch appears, as it surely will. The one thing that worries me is the constant insistance by Adobe personnel that they ‘can’t fix things they can’t reproduce’. Surely they don’t think we are all making these problems up. Of course, for commercial reasons, they’ll never admit that there’s a problem, but I’d love to be a fly on the wall at Adobe Towers!
The other worrying trend here is the release of products early because of a need to generate revenue – with us poor fools providing the feedback on bugs for free. As Bill Gates will testify, it doesn’t work. Windows Millenium Edition has become the defacto example of such folly. The cost of repairing something that wasn’t developed properly in the first place far outweighs the revenue shortfall created by hanging on for a few months – apart from the bad PR it generates. And what ever happened to beta and alpha versions?
We accept too readily these days that any new software is going to be problematical and full of bugs. Sad times indeed. Of course, if it were a TV or a DVD player, we could take it back. How about it Adobe? Could be a winner!
The one thing that worries me is the constant insistance by Adobe personnel that they ‘can’t fix things they can’t reproduce’.
<snirk!>
How can you fix something if you can’t reproduce it? How would you know if you’re changing the right thing? How would you know it’s fixed if it was never "broken" on your system to begin with?
Surely they don’t think we are all making these problems up.
If they did they wouldn’t keep trying to get you to define exactly when and where it fails. They’d simply say, it’s your system fix it. And don’t call me Shilry! <g>
Of course, if it were a TV or a DVD player, we could take it back.
You do have a 30 day money back guarantee. Keep providing info and Adobe will keep trying to replicate the problem. When they do, there’ll be a fix.
Hell, I do feel with him and with the many who have serious performance problems with CS. Let me say, I do not regret any penny ever spent on whatever Photoshop version, including this one, but also comparing to my past experience with PS, something does feel wrong about this release that you can’ blame only on the users.
Yes, I admit it is certainly very difficult to reproduce problems that pop up once a product gets run on so many different Hardware & OS configurations, but especially if those various setups seem to suffer such similar problems, there must be something at least "not so optimal" going on with the application itself.
The very odd scratch disk behavior I experience for example. I posted it already, but let me repeat here. Maybe some want to try it out too and it runs out I’m not alone with this?
Here is :
Clean Fresh Install of WinXP & service pack1 , 3 harddisks in my comp( 2 ata and 1 sata), all are running in Ultra DMA 5 mode, all are pretty new and fast. 7 partitions. No matter which harddisk or partition I dedicate as a scratch disk to CS, other than C ( yes, the OS system disk), would cause CS to take about more than 1 minute for startup and be slow in many simply processes, like moving layers, copying content from one file to the other etc… ( and I am not talking about huge files). As soon as I set the scratchdisk to C, all is rather fine. CS loads fast and performs quite well.
yesterday I even gave CS a freshly formatted clean 60 gigabyte partition at the beginning of the secondary harddisk, to digest and guess what; – it loads painfully slow. Alright, not really a problem after all, I’ll just give it the C scratch disk and have the OS use another partition on another drive.
But clearly this isn’t exactly the behavior that is meant to be. CS and all other Photoshop versions even give you a warning to not use the C drive as the scratchdisk.
I accidentally found that solution to my probs with CS, but it was actually not very likely I would come to this solution.
And honestly, I don’t really want to be forced to spend many hours fiddling around with and application just to get it to work. Neither do I have the time, nor do I think its wrong to expect something that isn’t exactly cheapware to have the basics functional as expected. Plus, I do keep my OS pretty clean and stable to make sure to provide the proper conditions for the software I work with and have to rely on.
something does feel wrong about this release that you can’ blame only on the users.
<cough>Activation<cough><cough>
at the beginning of the secondary harddisk,
is your second hard disk the master or slave on it’s channel? (or as we say in the politically correct PS Lounge, the "Mine" or "Mate"?)
My thinking is maybe it’ll run better if it’s set to the first partition of the master drive (on either primary or secondary channel) and there should be no slower device (cd-r, etc.) on the same channel.
I tried both master and slave and alone. apart from that with modern chipsets and motherboards it is not a problem anymore to have a slower and faster drive hooked together. they’ll run at their own speed each.
either way the difference in startup speed should not be THAT huge. ie 10 seconds or one and a half minute.
oh well. it was just a thought. there’s got to be something to it though since you say it works fine on the first partition of primary master…
ps7 doesn’t show that behavior btw. not at all.
and it doesn’t really seem to be a harddisk access speed issue, it seems more like CS gets confused and starts searching for something forever. it always "hangs" at loading the patterns. and if I am not hallucinating, it goes scanning all drives.
whatever.. I have it at c now and it works. its just weird though.
I too have many slow down performance problems with cs. when I call up filter gallery, I may as well go get a cup of joe. the first time I ask for FG it may take up to 2 minutes to get the window to apply the filters. after that it still responds slow but at least not the 2 mins. as the first time. I haven’t yet tried to change my PS scratch disk to C:, but will do it soon. when it comes to the C: drive, my system didn’t have a partition labeled C:. when I installed Win XP I used a sata raid for the system os. by doing that when install was done my main system disk was E: I have a total of 5 hd in my system. to make a long story shot, when I tried to install suite (CS) it would go through the routine, but did not actually install anything but some small printer routine. talked to adobe tech support and they said it would only install on a C: partition. I faked it by renaming a partition to C: installed the suite and then copied it all over to the normal os partition and placed all programs for CS under the normal "program files" directory. at least then the programs do work.
I can’t put my scratch to C because that’s pretty much full with the os. But i also think that CS is geting confused and is searching something when it "freezes". It feels that way here as well.
I didn’t have any problems installing CS on drive H, which is my programs ata raid.
So, we’re still working on it.
We’ve got some tests in progress – but they’re going to take a while.
And we still haven’t reproduced everything described here….
Photoshop CS takes 7 minutes for me to boot up…each time…I clock it. Also when using the Filter Gallery, it takes an extended amount of time. ImageReady takes a very, very long time to load as well.
I am using Windows XP Pro, with 1 GB ram with dual pentium 3 processors. If that is of any help.
Sweet-P
wrote in message
So, we’re still working on it.
We’ve got some tests in progress – but they’re going to take a while.
And we still haven’t reproduced everything described here….
I must say that i think Ph Cs is more an upgrade to 7.5 than a new product. U made more worse than good.
I Could write a paper on all the stuff i miss or dont like(updates)
But, I found many new and usable products.( as pointed to me by your seminarholder on your seminars)
But my highest sigh is the browser. How could u destroy a perfect product like this.( especially for 2 screens ).
But Imageready is werry nice:)
( i`ve been been using photoshop and the other products of adobe for 6 to 8 years.) Im currently working on a : 2 X 2,8Ghz xeon machine with 2Gbytes of RAM with 3dlabs wildcat 7110 ) )
I forgot to add my info:
p4, 2.7gig, ultraWide scsci, 53 gig hard disk space free, 512 mb ram, NVIDIA Quadro2Pro video card
Thanks to all of you for taking the time to add your scenarios. Jolayne
wrote in message
Hi
Need to jump in here. I upgraded to CS and have to confirm the slowness.
First i thought it is the new graphics card (matrox parhelia 128). So i switched back to my old one. Same result. Now i re-installed PS 7 and both graphic cards are just jamming.
So here is what happens.
Using CS, i can paint for a (short) while, then it starts to lag and i
hear that the pc is starting to swap on the disks. My taskmanager still tells me 600 Mb (out of 2gig) available.
Anyway, it gets worse and worse the longer i work in CS. Zooming in or out
makes the screen go white and i can watch how PS slowly rebuilds the screen. (that’s why i originally thought that i have a problem with my graphics card)
So i went back to PS 7, paint on the same image without any lag, without
any problem. Zoom in and out at will.
here’s some specs:
amd 2000+
abit kra7 raid mobo
lots of disks
2gig of RAM
wildcat vp870 (matrox parhelia 128) am running two monitors.
Now that i have tried all 4 combinations between PS 7 and PS CS with the
two graphic cards i have to say that at least here on my setup Phostshop CS is so slow that i can’t use it.
just wanted to let you know.
momo
I do not use a network, nor do I use network printers. I am not even messing with the Browser except out of curiosity, but when I do, I have background processing turned off per other threads.
CS is slow.
Is there a problem with Adobe or other users accepting or believing this? Thanks you for your reply,
Jolayne
wrote in message
what operationg system momo. there have been reports of probs with win2k.
and there’s a thread to that effect somewhere. mostly seems related to networking or network printers (at least that’s what I get so far.) also the new browser can slow things down when it’s first creating thumbnails. turn off background processing and high quality thumbs in prefrences and see if that helps.
Thanks for confirming what we already all know. You did a great job recreating the problem.
Jolayne
wrote in message
Hi
Need to jump in here. I upgraded to CS and have to confirm the slowness.
First i thought it is the new graphics card (matrox parhelia 128). So i switched back to my old one. Same result. Now i re-installed PS 7 and both graphic cards are just jamming.
So here is what happens.
Using CS, i can paint for a (short) while, then it starts to lag and i
hear that the pc is starting to swap on the disks. My taskmanager still tells me 600 Mb (out of 2gig) available.
Anyway, it gets worse and worse the longer i work in CS. Zooming in or out
makes the screen go white and i can watch how PS slowly rebuilds the screen. (that’s why i originally thought that i have a problem with my graphics card)
So i went back to PS 7, paint on the same image without any lag, without
any problem. Zoom in and out at will.
here’s some specs:
amd 2000+
abit kra7 raid mobo
lots of disks
2gig of RAM
wildcat vp870 (matrox parhelia 128) am running two monitors.
Now that i have tried all 4 combinations between PS 7 and PS CS with the
two graphic cards i have to say that at least here on my setup Phostshop CS is so slow that i can’t use it.
just wanted to let you know.
momo
"So, we’re still working on it. "
good to know 🙂
Turn off the File Browser High Quality Previews preference.
-Scott
Am I right in thinking that CS doesn’t use the MMXCore extension as used in PS7? Or any of the Fastcore routines? Could that be contributing to the slowdown? Just a thought. Maybe a techie could enlighten me.
Maybe a techie could enlighten me.
One means on. Zero means off. Consider yourself enlightened. 🙂
Look in your Plugins>Extensions folder…….
Steve – no, CS has MMXCore and FastCore (which are specific to each version).
I’m also very disappointed in the performance of Photoshop CS. I wish I could get my money back for this piece of junk. Photoshop 7 runs perfectly on my machine, but CS is junk. I’m running a P4 3GHZ with 1GB of RAM, and a 256MB NVidia Graphics Card, and CS still won’t run efficiently. This program is totally worthless. I can’t be productive with junk software like this. I can’t believe Adobe would even release something this bad.
One of the main reasons I bought the upgrade was for the new text on a path feature. Every time a try and rotate the text around to where I want it, there’s a 15-20 second delay. I’m just always sitting here twiddling my thumbs waiting for this program to respond.
I’ve also noticed that each time I hit Save there’s about a five second delay before the file will actually start saving. This happens even on 72dpi images that are no more than 300kb in size. What the hell is going on? This is a major flaw!
I’ve also noticed a lot of people are blaming the slow performance on too many fonts activated in Suitcase. Well, I’m running the same amount of activated fonts as I did with Photoshop 7, and I never had one problem with performance. Just to test, I deactivated all my Suitcase fonts, but the slow problems still persist in CS, even after a reboot.
I’ve also played around with the memory/cache settings in the CS preferences, but none of these things have solved the problem either. It seems like the more I use this software, the more problems pop up.
The bottom line is that this version of Photoshop is not ready for prime time. It should never have been released until the bugs were worked out. After reading all these posts, at least I know that I’m not alone in having problems with this software. It’s just downright unusable. I’ve decided to put CS on a spare machine in case I need to process a 16 bit image, and just continue to run PS7 as my main application. I hope Adobe will issue a patch for these problems (and a public apology), but for now I guess we are just screwed.
As a side note, I purchased an additional copy of Photoshop CS for my second office. Since I haven’t opened that box yet (thank God!), I’m going to send it back for a refund. If Adobe fixes these problems I might consider buying another copy at a later time, but for now I’m sticking with version 7.
