Luminous Landscape Forum
Raw & Post Processing, Printing => Digital Image Processing => Topic started by: Lisa Nikodym on February 18, 2008, 01:17:52 pm
-
I've had CS3 on my PC for many months now. Since I got a new PC a couple of months ago, opening files and printing have been blindingly fast. However, in the last week or two, this suddenly changed. Now, it takes 16 seconds to open a file, and 10 to 20 seconds to just navigate around the CS3 printing windows (for example, when the "Print" window is open and I click on the "Page Setup" button, it takes 10 to 20 seconds for it to pop up the Page Setup window). Once I'm inside the Epson print dialog windows, those are quick, but everything to do with the CS3 print windows is painfully slow. What used to take a fraction of a second now takes 10-20 seconds. As far as I know, I have not changed any CS3 settings.
I also have GIMP on the same machine, and it opens the same files quickly, so the problem seems to be specific to CS3. Has anyone else seen this problem recently? Or have any suggestions of things to try?
Thanks,
Lisa
-
Lisa,
try to change the ram the photoshop use to +
preferences -performance- memory usage
Blasr
-
When troubleshooting Photoshop it is always best to start by resetting preferences.
Hold down Alt, Ctrl, and Shift keys (Mac: Command, Option, Shift) while starting Photoshop. A dialog box will appear asking if you wish to delete the preferences file.
-
Things to check would include:
the amount of free space on the drive you use for CS3's scratch disk
the amount of free space on the drive you use for Windows' pagefile
whether you have recently and properly defragmented your hard drive(s).
whether you have added or upgraded or changed any anti virus software
whether you have changed the auto update settings (CS3 can run like a dog if it's trying to autoupdate and can't for some reason)
whether you have disabled graphics acceleration within CS3
whether you have "lost" any RAM (check available - if a module has failed, you'd have less, could be an issue)
-
Thanks, Farmer, but we checked all those things (except for "lost" RAM, which I checked just after your suggestion), and none of those are a problem. (Also checked BlasR's suggestion, and it has plenty of RAM.) It's a nearly brand-new PC (just had it a month or two) that has plenty of RAM, plenty of disk space, plenty of everything.
My spouse did a web search and found a number of people complaining about CS3 suddenly running very slowly, and reinstalling CS3 seemed to do the trick for at least some of them. Unless anyone has any other less time-consuming suggestions, in a few days I'll first try resetting the preferences file (probably not an issue, but just in case...) and then try reinstalling (ick).
Lisa
-
OK, I've found how to speed it up, but it's not pretty. I searched around Adobe's user forums and found other people having this problem (it sounds like it has probably been a problem just since a recent CS3 update, but that's not entirely clear). The problem occurs if your computer's default printer is a network printer. If you change the computer's default printer to a local printer, it fixes the problem. (In my case, I set it to some Microsoft Document Writer thing, since I don't have a non-network printer on my PC.)
On the other hand, this "dummy printer" is now the default printer for *all* other applications on my PC. For every other application that used to automatically go to my network laserjet, I now have to manually change the printer. Not a happy state of affairs.
I searched through the Adobe web site's support section and found nothing on this issue there. It was only in searching around the user forums there that I happened to find this information! I do hope they issue a bug fix soon to avoid this problem, so I can set my default printer back the way it was...
Lisa
-
That's very interesting regarding the network printer issue!
Are you using CS3 10.0.1 (I presume you are and that's what you mean by the latest update)?
Are you just using Photoshop or any of the other suite of programs?
I'm curious because, here at work, all my workstations and test stations connect to printers on the network by default, (and that's a fairly large corporate network), and CS3 isn't giving me any problems whether it be a default printer set to one of the lasers or one of the large formats.
At home, my printers are also only on a network (a laser and a large format) and no issue so it would be interesting to try to discover what the main differences are to see if this can be fixed for you by identifying the source of the problem.
Does your network printer connect using a standard TCP/IP port or a custom port/software of some sort? Is it a static IP or dynamic or using names instead of numbers? Are you running any custom firewalls or QOS packet checking or other network utilities? Are you using a hub or a router (unmanaged or managed) and it it 10, 100 or 1000?
-
I'm curious because, here at work, all my workstations and test stations connect to printers on the network by default, (and that's a fairly large corporate network), and CS3 isn't giving me any problems whether it be a default printer set to one of the lasers or one of the large formats.
At home, my printers are also only on a network (a laser and a large format) and no issue so it would be interesting to try to discover what the main differences are to see if this can be fixed for you by identifying the source of the problem.
[a href=\"index.php?act=findpost&pid=176051\"][{POST_SNAPBACK}][/a]
The odds are (and it's been an issue for Photoshop on Win for several versions) is where there is a networked printer set as the default and for some reason, the networked printer isn't available...the problem, (slowdown) is multiple and repeated attempts to connect to the printer that isn't available.
The solution is to use a non-networked printer as "default" or make sure the printer IS available before launch.
-
I agree, Jeff, that's got to be what's causing the problem. What I'm trying to do is identify what's causing the printer to not be available so that Lisa doesn't need to have her system set to a default printer that's of no use to her - particularly as this appears to have been a recent occurrence there may be a change that can be reverted or dealt with.
-
Are you using CS3 10.0.1 (I presume you are and that's what you mean by the latest update)?
Are you just using Photoshop or any of the other suite of programs?
I'm curious because, here at work, all my workstations and test stations connect to printers on the network by default, (and that's a fairly large corporate network), and CS3 isn't giving me any problems whether it be a default printer set to one of the lasers or one of the large formats.
At home, my printers are also only on a network (a laser and a large format) and no issue so it would be interesting to try to discover what the main differences are to see if this can be fixed for you by identifying the source of the problem.
Does your network printer connect using a standard TCP/IP port or a custom port/software of some sort? Is it a static IP or dynamic or using names instead of numbers? Are you running any custom firewalls or QOS packet checking or other network utilities? Are you using a hub or a router (unmanaged or managed) and it it 10, 100 or 1000?
OK, let's take the questions one by one:
Yes, I'm using version 10.0.1.
I am just using Photoshop (CS3), Bridge and ACR. Nothing else from Adobe (except Acrobat Reader).
The Epson printer is actually directly connected via a USB connection to my spouse's computer (which runs Windows XP home; mine is Windows Vista 32-bit); our computers are connected together via 100 base T. Our computers get their dynamic addresses through DHCP. There is also a firewall/router to isolate our network from the outside world. Both computers are running "Windows 1-Care" firewalls, and they haven't reported trying to block any attempts at connecting the computers (which they would if it were happening). There are no other firewalls, QOS packet checking, or other things like that. Printing from other Windows applications to the former default printer (a B&W laserjet) goes quickly without problems. It's a pretty plain-vanilla home network.
Everything was working great up to something like two weeks ago, when the slowness started, and we don't know of anything we consciously changed at that point (though all sorts of things auto-update, so it's always possible something changed that way). It isn't a simple case of the default printer being "not ready", since it happily prints from other applications (for example, MS Word) I run. I agree, somehow CS3 must be getting the erroneous idea that the printer isn't available for some reason.
Thanks very much, Farmer, for giving this some thought. I'd be very interested if you can give us any insight on the problem.
Lisa
-
I'll have more of a think about this when I get home, but off the top of my head seeing Vista and XP Home there and now understanding the topology of your network, I would suggest it's some sort of security related issue.
The two operating systems rely on communicating with each other to basically establish a level of trust depending upon who is logged in and with what privileges to each machine. It can sometimes happen, for example, that you will see that a network mapped drive is not displaying available disk space until you click on it to force it to refresh. A similar thing may be happening here. It's going to be tricky to figure out exactly what, but a few questions along that line:
Do both users have accounts with the same password on both machines and do both have the same level of access (Local administrator being optimal)?
Does the printer on your spouse's computer have all the Epson software installed (Driver, Status Monitor and, if it's a large format (3800 or above) Remote Panel)?
If it has Status Monitor installed, have you checked the options to allow Network Monitoring?
The other path that's coming to mind is that perhaps power saving options have changed. Worth double checking even though it's unlikely without you explicity choosing to do so.
-
Do both users have accounts with the same password on both machines and do both have the same level of access (Local administrator being optimal)?
We actually use the same username and password on both PCs; both have administrator privileges.
Does the printer on your spouse's computer have all the Epson software installed (Driver, Status Monitor and, if it's a large format (3800 or above) Remote Panel)?
We have the drivers, status monitor and remote panel installed for the 3800 (on my spouse's PC, but not mine), though we never use the remote panel. However, the former default printer on my computer (the one that seems to be causing the trouble) is not the 3800, but a Brother laserjet that gets used for everything except photos.
The other path that's coming to mind is that perhaps power saving options have changed. Worth double checking even though it's unlikely without you explicity choosing to do so.
If you're asking about the PCs, the only power saving we have on is to blank the monitor after some amount of time. Otherwise, we just manually turn them off when we won't be using them for awhile. (And that's the way we've always had it.) If you're asking about the laserjet printer (the former default printer), it's permanently on but in "sleep" mode until something gets sent to it (in which case it "wakes up" and prints). I just tried the experiment of setting the default printer *back* to the laserjet, printing an image to the laserjet in order to make sure it's currently "awake", and then trying to open the print window again - the result is, it's still slow. (So much for the "maybe the problem is the sleeping printer" theory...)
Well, it's time to get ready for bed here, so I'll check in again tomorrow morning...
Thanks,
Lisa
-
Just a thought, didn't CS or CS2 have a cache that needed to be cleaned or it slowed down? I'm sure I remember that problem mentioned before somewhere, maybe CS3 has the same?? Wayne
-
Lisa,
Since you are now in desperation mode, I'll throw in my 2 cents (but allow for depreciation).
I found CS3 much slower than CS2 when I first installed it, and I had lots of problems with slow file loading and saving (I usually don't print from inside CS, so I don't know if printing was affected). Among other fixes, I tried upping (in preferences) the amount of ram for Photoshop, but things seemed to get even worse. Then I read somewhere that plugins generally use memory that isn't part of Photoshop's allotment, so I tried lowering the Photoshop memory to the minimum recommended (low end of what PS calls the "ideal range"), and indeed things sped up by a good bit.
I have done one other thing which has helped. For my XP Pro desktop I installed a utility called "EBoostr" which uses fast USB thumbdrives as a general cache. This seems to have made a significant difference.
I believe that Vista has such a feature built in, called "Vboost", I think. If you haven't done so, I suggest getting a fast thumbdrive or two and engaging Vboost.
I hope this helps. Do let us know what you eventually figure out.
-Eric
P.S. The behavior I had when CS3 was running slow sounds very much like your printer experience, but with saving or loading of files. When I saved a file in CS3, nothing would happen for sometimes 30 seconds or more, as if the hard drive had gone to sleep (impossible). By clicking on various parts of the CS3 window until I got a "CS3 not responding" message, or even trying to see what was happening in Task Manager, it would eventually wake up and save the file (very slowly).
What I believe was happening was a lot of file thrashing as parts of Windows' own file handling processes were being swapped in and out of memory because there was not enough memory left outside of Photoshop to do the simplest routines. The same might be happening with your printing.
-
Seems like you've covered most things already, Lisa, so I'm really stumped at this point. Setup looks fine and I wouldn't expect it to be causing you a problem.
I presume your 3800 is on the network by itself, rather than shared via a PC? Is there any option to do this with the laser?
From what I can see, Adobe Engingeer Chris Cox has confirmed what's happening and there's no apparent "fix" from within Photoshop other than changing the default printer. Refer to http://blogs.adobe.com/jnack/2007/10/tuning_photosho.html (http://blogs.adobe.com/jnack/2007/10/tuning_photosho.html) and check the last comment. You might like to leave a note of your own to see if John Nack ever received any further updates (seems likely not, since Chris responded) or to propose they look at an option to turn off that behaviour?
Since you tried having the printer "awake" and that didn't help, my last guess is that some change or tweak with Vista has changed the way or the speed with which it interogates the printer to send the information back to Photoshop.
Only other suggestion would be to swap the current arrangement - hook the laser directly to your PC and share it so your spouse can see it over the network.
I'm sorry we seem to have come to a dead end in resolving this better
-
I presume your 3800 is on the network by itself, rather than shared via a PC? Is there any option to do this with the laser?
I'm not quite sure I understand the question. Both printers are currently hooked directly into my spouse's PC via USB ports.
Since you tried having the printer "awake" and that didn't help, my last guess is that some change or tweak with Vista has changed the way or the speed with which it interogates the printer to send the information back to Photoshop.
I agree that your assessment is probably correct.
Only other suggestion would be to swap the current arrangement - hook the laser directly to your PC and share it so your spouse can see it over the network.
Interesting suggestion. We'll try that this weekend and see if it fixes the problem.
Thanks very much for your advice and the effort you've put into thinking about this problem, Farmer. I'll post back when I find out whether moving the laserjet to my PC worked. It will take awhile, however (it may involve physically moving the printer, since it may not be close enough to my PC for a USB cable to work well), so it will probably have to wait for the weekend.
Thanks again
Lisa
-
I'm not quite sure I understand the question. Both printers are currently hooked directly into my spouse's PC via USB ports.
[a href=\"index.php?act=findpost&pid=176346\"][{POST_SNAPBACK}][/a]
The 3800 comes with a built in network port, so you could move that onto your network (which means you don't need your spouse's PC to be on to access it) and it's possible that changing that could affect things overall and for the better. It is a better way to network the printer rather than just through print sharing as you currently have it.
There are multiple ways to achieve this depending on your network setup generally and your level of technical experience. If you wanted to try it and need a hand, feel free to post or drop me a PM.
-
I have no solutions, but thought I would mention that I too have had similar problems and some additional ones. I had been working on large (500 MB) files with CS on a Pentium 4 with 2 GB. When I got CS3, I upgraded the computer to a dual core with 4 GB (XP pro, 3GB switch on). Much to my surprise, the new system was not faster and at times became very slow (e.g., 3 min to rotate, 3 min to save a file). CS3 seems to have some memory leak problems; even after a file is closed, PS is using 2 GB of RAM. The only way I have found to free up that RAM is to close PS and restart. Perhaps related to some previous comments is the occasional message I get when trying to print: PS3 will tell me I need to install a printer if I want to print (Epson 4800 is the default). My usual work around is to save the file and print from CS, or reopen CS3. The last time this happened, I tried to save the file and CS3 informed me that there was insufficient RAM to save! I then opened a different file, closed it, and was then allowed to save the original file. I have not had time to pursue these problems and was simply trying to get some prints ready.
-
I have no solutions, but thought I would mention that I too have had similar problems and some additional ones. I had been working on large (500 MB) files with CS on a Pentium 4 with 2 GB. When I got CS3, I upgraded the computer to a dual core with 4 GB (XP pro, 3GB switch on). Much to my surprise, the new system was not faster and at times became very slow (e.g., 3 min to rotate, 3 min to save a file). CS3 seems to have some memory leak problems; even after a file is closed, PS is using 2 GB of RAM. The only way I have found to free up that RAM is to close PS and restart. Perhaps related to some previous comments is the occasional message I get when trying to print: PS3 will tell me I need to install a printer if I want to print (Epson 4800 is the default). My usual work around is to save the file and print from CS, or reopen CS3. The last time this happened, I tried to save the file and CS3 informed me that there was insufficient RAM to save! I then opened a different file, closed it, and was then allowed to save the original file. I have not had time to pursue these problems and was simply trying to get some prints ready.
[a href=\"index.php?act=findpost&pid=176537\"][{POST_SNAPBACK}][/a]
Memory management is a tricky subject.
The /3GB switch is useful, but potentially dangerous. If you don't leave enough RAM for the operating system, it will be constantly paging out to disk and that will bring your system to a halt (particularly if it decides it needs to expand your pagefile). There are many other settings that need to be considered before using /3GB with confidence (first and foremost being /userva to ensure system stability by controlling how much RAM is left for the OS).
You also need to look at your history states and other things that will blow out your scratch sizes (you set to see that rather than basic image size). Every time you do something the history has to record the previous version and that takes memory. It's very easy to turn a 500MB file into several GB of disk space needed for the current iteration with history, layers, etc.
So if you're using most of your RAM for PS and the OS is paging out all the time and if you don't have enough physical RAM (and you won't) for the scratch size of your image, then PS is swapping out to disk as well. If they happen to be the same disk it gets even worse.
You're right - you need to restart to free the memory or you need to clear your history.
-
Perhaps related to some previous comments is the occasional message I get when trying to print: PS3 will tell me I need to install a printer if I want to print (Epson 4800 is the default). My usual work around is to save the file and print from CS, or reopen CS3.
You're not the only one...I was having the same problem with CS3 a few months ago, and was unable to figure out what was causing it. In my case it wasn't just occasional, but all the time (once it started happening). I too just started printing from CS2 (which worked) until we moved the printer off the network port and onto a direct USB connection to another PC in the network, which seemed to fix it.
CS3 seems to have a lot more problems than all the previous versions I've used (PS4, PS6, CS, CS2).
Lisa
-
CS3 seems to have some memory leak problems; even after a file is closed, PS is using 2 GB of RAM.
[a href=\"index.php?act=findpost&pid=176537\"][{POST_SNAPBACK}][/a]
No...that's NOT a memory leak...a "leak" is where small amounts of raw get fragmented to the point where is is then set to be idle (unusable) by the system until a reboot...
Photoshop is DESIGNED to not free up ram it has asked the system for until (and unless) idle for quite some time or until the SYSTEM requests it because another app needs it. If you have Photoshop running in the background with nothing open over time (dictated by the OS) ram will get freed up.
-
Any disconnected network drives?:
http://blogs.technet.com/markrussinovich/a...orer-hangs.aspx (http://blogs.technet.com/markrussinovich/archive/2005/08/28/the-case-of-the-intermittent-and-annoying-explorer-hangs.aspx)
-
Memory management is a tricky subject.
The /3GB switch is useful, but potentially dangerous. If you don't leave enough RAM for the operating system, it will be constantly paging out to disk and that will bring your system to a halt (particularly if it decides it needs to expand your pagefile). There are many other settings that need to be considered before using /3GB with confidence (first and foremost being /userva to ensure system stability by controlling how much RAM is left for the OS).
[{POST_SNAPBACK}][/a] (http://index.php?act=findpost&pid=176553\")
Phil:
CS3 is assigned 1.7GB (About 71% of the amount PS thinks is available); since the system recognizes 3.25 GB, there should be plenty for the OS.
You also need to look at your history states and other things that will blow out your scratch sizes (you set to see that rather than basic image size). [a href=\"index.php?act=findpost&pid=176553\"][{POST_SNAPBACK}][/a]
History is set to 1; scratch discs are D and E; CS3 is on C
No...that's NOT a memory leak...a "leak" is where small amounts of raw get fragmented to the point where is is then set to be idle (unusable) by the system until a reboot...
[a href=\"index.php?act=findpost&pid=176565\"][{POST_SNAPBACK}][/a]
Jeff perhaps it is not technically a leak, but it has the same effect. I open a file, work on it, save, open another, within a short time PS is using all the allocated (1.7 GB) RAM even through I have saved and closed all files. I then open the next file and see an efficiency less than 100%; the only way to clear the RAM is to close CS3.
Any disconnected network drives?:
[a href=\"http://blogs.technet.com/markrussinovich/archive/2005/08/28/the-case-of-the-intermittent-and-annoying-explorer-hangs.aspx]http://blogs.technet.com/markrussinovich/a...orer-hangs.aspx[/url]
[a href=\"index.php?act=findpost&pid=176578\"][{POST_SNAPBACK}][/a]
Nope, but thanks
-
CS3 is assigned 1.7GB (About 71% of the amount PS thinks is available); since the system recognizes 3.25 GB, there should be plenty for the OS.
If you're not assigning more than 2GB to Photoshop there's really no need for the /3GB switch. You might want to consider turning it off. You will reduce (even if you got to say 80%) the amount of allocation but not by a lot. See how system stability goes. If it's better, then the problem is there. You can then read up on /userva switch and make use of it to re-enable /3GB with more control.
History is set to 1; scratch discs are D and E; CS3 is on C
Ideally you want a single scratch disk that has nothing else on it (even if it's just a partition on a drive that isn't accessed for much else) and you want it on a different drive to your Windows Pagefile which would enjoy the same sort of isolation (and a fixed size of 4GB is ideal).
Jeff perhaps it is not technically a leak, but it has the same effect. I open a file, work on it, save, open another, within a short time PS is using all the allocated (1.7 GB) RAM even through I have saved and closed all files. I then open the next file and see an efficiency less than 100%; the only way to clear the RAM is to close CS3.
That's working normally and, normally, it's not a problem. Something else is getting into the mix and causing your issues I reckon.
Honestly, I'd turn off /3GB to start with and see what happens - it's still possible that some driver is mapping to a part of memory that you're now attempting to access because of the switch and fine tuning with /userva could help.
-
If you're not assigning more than 2GB to Photoshop there's really no need for the /3GB switch. You might want to consider turning it off. You will reduce (even if you got to say 80%) the amount of allocation but not by a lot. See how system stability goes. If it's better, then the problem is there. You can then read up on /userva switch and make use of it to re-enable /3GB with more control.
Ideally you want a single scratch disk that has nothing else on it (even if it's just a partition on a drive that isn't accessed for much else) and you want it on a different drive to your Windows Pagefile which would enjoy the same sort of isolation (and a fixed size of 4GB is ideal).
That's working normally and, normally, it's not a problem. Something else is getting into the mix and causing your issues I reckon.
Honestly, I'd turn off /3GB to start with and see what happens - it's still possible that some driver is mapping to a part of memory that you're now attempting to access because of the switch and fine tuning with /userva could help.
[a href=\"index.php?act=findpost&pid=176760\"][{POST_SNAPBACK}][/a]
Phil, thanks for the input, I will look at /userva. I should say that I started with 2GB and CS3 was too slow, so I increased to 4 GB and added the /3GB switch. I should also mention that if I have Bridge running, it uses over 0.5 GB of additional RAM which takes the system over the 2GB available without the switch. I tried allocating more than 70% of RAM to CS3, but no increase in speed, just more RAM usage.
-
Phil, thanks for the input, I will look at /userva. I should say that I started with 2GB and CS3 was too slow, so I increased to 4 GB and added the /3GB switch. I should also mention that if I have Bridge running, it uses over 0.5 GB of additional RAM which takes the system over the 2GB available without the switch. I tried allocating more than 70% of RAM to CS3, but no increase in speed, just more RAM usage.
[a href=\"index.php?act=findpost&pid=176807\"][{POST_SNAPBACK}][/a]
The 2GB limit is *per application* and exceeding this requires both the /3GB switch *and* an application capable of making use of the additional address space. Note that memory management allows any application to deal with data in excess of 2GB regardless of the switch so long as the application itself is designed to deal with such large amounts of data.
More RAM only helps to a point. I have one image, for example, that is 3.5GB on disk. Opening that into Photoshop immediately causes a scratch size of just over 9GB. Under Vista 64 (which I am testing at the moment) I can see all of the 4GB that I have installed (compared to the 3.5GB out of 4GB that I can see under XP), but even if I had 8GB (the most my main board will support) under Vista 64 it still wouldn't be enough to completely contain this image, with its layers etc. And that's not even taking into consider that the operating system and application would some RAM anyway. Image size on disk can blow out to *much* higher scratch values very easily, which means accessing hard drives as scratch space.
The only way to really improve that performance is to improve the i/o performance of the scratch disk. This could include things such as the use of raptors, or 15k rpm scsi disks, or RAID 0 (striping), or move to flash RAM drives or, if I have unlimited funds, use a series of volatile RAM drive devices (but even then I'm limited to the speed of the PCI-X or PCI-E bus). None of those will be as fast as straight RAM but you can see substantial benefits using, say, a couple of raptors in RAID 0.
-
More RAM only helps to a point. I have one image, for example, that is 3.5GB on disk. Opening that into Photoshop immediately causes a scratch size of just over 9GB. Under Vista 64 (which I am testing at the moment) I can see all of the 4GB that I have installed (compared to the 3.5GB out of 4GB that I can see under XP), but even if I had 8GB (the most my main board will support) under Vista 64 it still wouldn't be enough to completely contain this image, with its layers etc. And that's not even taking into consider that the operating system and application would some RAM anyway. Image size on disk can blow out to *much* higher scratch values very easily, which means accessing hard drives as scratch space.
[a href=\"index.php?act=findpost&pid=176820\"][{POST_SNAPBACK}][/a]
6 or so years back I was handling 750+M images with what ever version of PS was around then, I probably had 512M of RAM and by today's standards a very weedy chip and yet PS coped no problem. PS definitly seems slower than it used to and my files sizes currently are not as big as when handling multilayered film scans.
-
The 2GB limit is *per application* and exceeding this requires both the /3GB switch *and* an application capable of making use of the additional address space. Note that memory management allows any application to deal with data in excess of 2GB regardless of the switch so long as the application itself is designed to deal with such large amounts of data.
More RAM only helps to a point. I have one image, for example, that is 3.5GB on disk. Opening that into Photoshop immediately causes a scratch size of just over 9GB. Under Vista 64 (which I am testing at the moment) I can see all of the 4GB that I have installed (compared to the 3.5GB out of 4GB that I can see under XP), but even if I had 8GB (the most my main board will support) under Vista 64 it still wouldn't be enough to completely contain this image, with its layers etc. And that's not even taking into consider that the operating system and application would some RAM anyway. Image size on disk can blow out to *much* higher scratch values very easily, which means accessing hard drives as scratch space.
The only way to really improve that performance is to improve the i/o performance of the scratch disk. This could include things such as the use of raptors, or 15k rpm scsi disks, or RAID 0 (striping), or move to flash RAM drives or, if I have unlimited funds, use a series of volatile RAM drive devices (but even then I'm limited to the speed of the PCI-X or PCI-E bus). None of those will be as fast as straight RAM but you can see substantial benefits using, say, a couple of raptors in RAID 0.
[{POST_SNAPBACK}][/a] (http://index.php?act=findpost&pid=176820\")
With a 64 bit processor Photoshop CS3 is capable of utilizing ram above 4 gigs as scratch disk before going to the hard drive. So more ram will actually speed up the system. All the info is included in this Adobe Tech note:
[a href=\"http://www.adobe.com/go/kb401088]http://www.adobe.com/go/kb401088[/url]
dooode
-
With a 64 bit processor Photoshop CS3 is capable of utilizing ram above 4 gigs as scratch disk before going to the hard drive. So more ram will actually speed up the system. All the info is included in this Adobe Tech note:
http://www.adobe.com/go/kb401088 (http://www.adobe.com/go/kb401088)
dooode
[a href=\"index.php?act=findpost&pid=176978\"][{POST_SNAPBACK}][/a]
It's not the processor, but the OS that counts. The OP is using Windows XP Home (32bit) and Windows Vista (32bit) so none of that applies in this case.
Of course a 64bit machine (processor and OS) can address higher areas of RAM.
-
It's not the processor, but the OS that counts. The OP is using Windows XP Home (32bit) and Windows Vista (32bit) so none of that applies in this case.
Of course a 64bit machine (processor and OS) can address higher areas of RAM.
[a href=\"index.php?act=findpost&pid=177004\"][{POST_SNAPBACK}][/a]
The Adobe Tech note is very relevant, covering memory optimization on both 32 and 64 bit operating systems.
You should take the time to read it.
-
The Adobe Tech note is very relevant, covering memory optimization on both 32 and 64 bit operating systems.
You should take the time to read it.
[a href=\"index.php?act=findpost&pid=177020\"][{POST_SNAPBACK}][/a]
I've read it many times and referred countless people to it.
Here are the important parts of what you're talking about that confirm what I'm saying:
Photoshop CS3 is a 32-bit application. When it runs on a 32-bit operating system, such as Windows XP Professional and some versions of Windows Vista, it can access the first 2 GB of RAM on the computer.The operating system uses some of this RAM, so the Photoshop Memory Usage preference displays only a maximum of 1.6 or 1.7 GB of total available RAM. If you are running Windows XP Professional with Service Pack 2, you can set the 3 GB switch in the boot.ini file, which allows Photoshop to use up to 3 GB of RAM.
And here:
When you run Photoshop CS3 on a computer with a 64-bit processor (such as a, Intel Xeon processor with EM64T, AMD Athlon 64, or Opteron processor) running a 64-bit version of the operating system (Windows XP Professional x64 Edition or Windows Vista 64-bit) and with 4 GB or more of RAM, Photoshop will use 3 GB for it's (sic) image data.
Please note the:
running a 64-bit version of the operating system
As I've said, with a 32bit operating system you are limited to 2GB per application of physical RAM. It can use substantially more virtual memory, which is why you can open files larger than 2GB, but unless you use the /3GB switch 2GB is the absolute maxiumum that the application can use regardless of the amount of RAM physically in the computer and regardless of whether the processor can run in 64bit mode.
WHEN you run a 64bit operating system, Photoshop can use more RAM in CS3 both directly for image data and then other areas of the higher mapped RAM for plugins and caching. This is NOT possible when running a 32bit operating system such as the OP regardless of the amount of physical RAM and regardless of the processor being capable of handling 64bit instructions.
Thanks.
-
Phil:
One more question, in response to my statement:” Jeff perhaps it is not technically a leak, but it has the same effect. I open a file, work on it, save, open another, within a short time PS is using all the allocated (1.7 GB) RAM even through I have saved and closed all files. I then open the next file and see an efficiency less than 100%; the only way to clear the RAM is to close CS3.” You replied:
That's working normally and, normally, it's not a problem. Something else is getting into the mix and causing your issues I reckon.
[a href=\"index.php?act=findpost&pid=176760\"][{POST_SNAPBACK}][/a]
CS does not behave this way on the same system, only CS3, ant idea of what the “something else” is?
Lisa, if you are still following this thread, you said:
CS3 seems to have a lot more problems than all the previous versions I've used (PS4, PS6, CS, CS2).
Lisa
[a href=\"index.php?act=findpost&pid=176558\"][{POST_SNAPBACK}][/a]
I have had other problems with CS3 beyond those discussed here, such as CS3 announcing it has encountered an error and needs to close, thus losing all my work. This never happened with CS, so I agree.
On a different topic, I saw a post of yours awhile ago and I meant to respond, but never did. Seems you and I passed through the Kyoto train station at the same time (or darn close). Attached is a photo taken 3/30/06. I had been there 3 days earlier as well
-
I have had other problems with CS3 beyond those discussed here, such as CS3 announcing it has encountered an error and needs to close, thus losing all my work. This never happened with CS, so I agree.
Admittedly, all CS3 problems that were not mostly of my own making are related to printers and printing, though the problems take different forms at different times. It's possible there's really just one underlying problem with the way printing is set up that crops up in different forms under different conditions. Whatever it was, I never had these problems with earlier versions of PS.
Of course, there was also the problem of improper uninstallation of the beta release screwing up the behavior of CS3; that was sort of a bug in the sense that it was very easy for people to fall into that trap, and difficult for them to figure out why things aren't working right. I had a similar pseudo-bug in which I thought I could just copy most of my plug-ins from CS2 to CS3 without uninstalling and reinstalling them (which seems a reasonable assumption); it didn't tell me what the problem was, I just had weird crashes and serious CS2 misbehaviors that appeared unrelated to the plug-ins, and it took assistance from this forum to point me to the cause. It's unfortunate when software is such that it's easy for users to fall into such traps and the software isn't smart enough to tell the user what they're doing wrong.
We haven't tried moving printers around yet to try to solve the "can't find the printer" problem - that's on today's to-do list...
On a different topic, I saw a post of yours awhile ago and I meant to respond, but never did. Seems you and I passed through the Kyoto train station at the same time (or darn close). Attached is a photo taken 3/30/06. I had been there 3 days earlier as well
Amusing! And I like your photo. I found it really tough to get a photo of the Kyoto train station that was any good at giving the impression of how high and huge it is. It was one of the best parts of Kyoto, IMHO. If you're ever back, it also had the best restaurants we found in Japan, in the clump of restaurants around the 10th or 11th level about street level - a fantastic tempura restaurant and a fantastic tonkatsu restaurant.
Lisa
-
OK, an update on my attempts to fix the printer-related slowness problem. We moved both the Epson and the laserjet to network connections, both served by my PC (the one with CS3), and it now all seems to work well and quickly again. It appears that having them both directly connected via USB to another PC on the network causes CS3 to have problems. Also, from what we found some months earlier, having the Epson on a network connection but served by another PC on the network *also* caused problems.
We had previously been serving the Epson on my spouse's PC because my elderly PC was too old & slow to let me continue working while it was sloooowly spooling the print job to the printer. That's no longer a problem since I got a fast new PC, so the current setup is acceptable.
Many thanks to Farmer and others here for assistance in figuring this out.
Lisa
-
Lisa - great news that you've found a resolution :-)
CS does not behave this way on the same system, only CS3, ant idea of what the “something else” is?
[a href=\"index.php?act=findpost&pid=177056\"][{POST_SNAPBACK}][/a]
Honestly, no. I don't have any technical references handy regarding how CS handled caching. It's possible it was different and unloaded data more quickly (or loaded less in the first place). This assumes you have all settings the same between the two versions, of course.