![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Speed up Photoshop?
- Thread starter CAD OC'er
- Start date
Tony Montana
[H]ard|Gawd
- Joined
- Sep 11, 2001
- Messages
- 1,336
go into options and seletct that PS use 100% of memory i dotn know if you are doing that right now.
Inquisition
Limp Gawd
- Joined
- Oct 11, 2003
- Messages
- 353
100% use of memory is crippling dont do that..
set some scratch disks on indepedant drives..that should speed things up . yes harddrives do make a difference
set some scratch disks on indepedant drives..that should speed things up . yes harddrives do make a difference
Ice Czar
Inscrutable
- Joined
- Jul 8, 2001
- Messages
- 27,174
1. more RAM
2. a seperate HDD on a seperate channel for the scratch disk than from the pagefile\OS HDD
3. optimize the file your opening, if its fragmented to hell and back over the platter being on a fater drive is going to have limited impacxt if its still fragmented
http://www.hardforum.com/showthread.php?s=&threadid=741512
2. a seperate HDD on a seperate channel for the scratch disk than from the pagefile\OS HDD
3. optimize the file your opening, if its fragmented to hell and back over the platter being on a fater drive is going to have limited impacxt if its still fragmented
http://www.hardforum.com/showthread.php?s=&threadid=741512
Ice Czar
Inscrutable
- Joined
- Jul 8, 2001
- Messages
- 27,174
hmmm...missed that
well photoshop itself is limited to 2GB as a process
as would be the OS likely, meaning a given process cant employ greater than 2GB, the OS "in total" can likely deal with 4GB
(a 64bit OS differs, but it would still be limited by the ap, Photoshop has no plans to up that)
If you where running more than 2GB you could devote a full 2GB to Photoshop and the rest would be for other aps, background processes and the OS, but you likely wouldnt see a great increase in performance and it also wouldnt impact the open\save issue
in thus case RAM isnt the factor slowing opening or saving
opening Photoshop itself is slowed by loading up the various elements which if Im not mistaken also includes checking installed fonts, if your able to keep the ap and fonts defragmented and near the outer diameter of any given HDD platter youll get both lower latency and higher sequential transfer
as opposed to the armeture flailing around all over the disk accessing bits here and there
same goes with reading the file your opening or writing the file your saving
most of the time Im saving a file, I have no problem since it being written to the RAID5 array and rarely exceeds the on card cache (128MB), the initial opening is another matter since often its being read from a flash drive. opening a PSD generally isnt so bad since its been saved to the RAID5 and reads are quite good across 6 HDDs (WD 40GBs)
while investing in faster drives would likely improve both your reads and writes
as Inquisition pointed out optimizing your disks first is a good idea
ideally 3 disks (or disks & arrays) on three channels
1. OS\ap\pagefile say IDE0\Master accesses > opening the ap, checking fonts, OS memory paging
2. Scratchdisk say IDE1\Master > Ap memory paging and history
3. Storage Disk or array PCIcard > read from load into memory and save to.
seperate channels avoids any concurrent access problems
seperating your Performance space from your storage space and keeping all of it optimally located and defragmented can pay big dividends
if you cant swing 3 channels & drives, seperating 1&2 effects ap performance the most
3 effects opening and saving, you can also employ partitioning to forstall fragmentation see my 1st link above
you might get as much bang for you buck from a $25 PCI controller card, a 20GB 7200rpm HDD and a good defrag ap as you would out of a 10k Raptor
(depends on your current level of optimization)
and as mikeblas pointed out learning to measure and log your performance is a good idea
Start > Run > (type) perfmon.msc > help
well photoshop itself is limited to 2GB as a process
as would be the OS likely, meaning a given process cant employ greater than 2GB, the OS "in total" can likely deal with 4GB
(a 64bit OS differs, but it would still be limited by the ap, Photoshop has no plans to up that)
If you where running more than 2GB you could devote a full 2GB to Photoshop and the rest would be for other aps, background processes and the OS, but you likely wouldnt see a great increase in performance and it also wouldnt impact the open\save issue
in thus case RAM isnt the factor slowing opening or saving
opening Photoshop itself is slowed by loading up the various elements which if Im not mistaken also includes checking installed fonts, if your able to keep the ap and fonts defragmented and near the outer diameter of any given HDD platter youll get both lower latency and higher sequential transfer
as opposed to the armeture flailing around all over the disk accessing bits here and there
same goes with reading the file your opening or writing the file your saving
most of the time Im saving a file, I have no problem since it being written to the RAID5 array and rarely exceeds the on card cache (128MB), the initial opening is another matter since often its being read from a flash drive. opening a PSD generally isnt so bad since its been saved to the RAID5 and reads are quite good across 6 HDDs (WD 40GBs)
while investing in faster drives would likely improve both your reads and writes
as Inquisition pointed out optimizing your disks first is a good idea
ideally 3 disks (or disks & arrays) on three channels
1. OS\ap\pagefile say IDE0\Master accesses > opening the ap, checking fonts, OS memory paging
2. Scratchdisk say IDE1\Master > Ap memory paging and history
3. Storage Disk or array PCIcard > read from load into memory and save to.
seperate channels avoids any concurrent access problems
seperating your Performance space from your storage space and keeping all of it optimally located and defragmented can pay big dividends
if you cant swing 3 channels & drives, seperating 1&2 effects ap performance the most
3 effects opening and saving, you can also employ partitioning to forstall fragmentation see my 1st link above
you might get as much bang for you buck from a $25 PCI controller card, a 20GB 7200rpm HDD and a good defrag ap as you would out of a 10k Raptor
(depends on your current level of optimization)
and as mikeblas pointed out learning to measure and log your performance is a good idea
Start > Run > (type) perfmon.msc > help
P4 2.8E @ 3.2 on an Abit IS7-GRandysWay said:
2x TWINX1024-3200C2PT
1x 36 WD Raptor for XP Pro
BTW my average layout is on 11x17 600 dpi or 24x36 300 dpi. I create site plans, renderings, and those big and small maps you see in malls that say "You are here"