Results 1 to 7 of 7

Thread: Adobe PS CS5 plugin to speed file saves

  1. #1
    BPN Viewer
    Join Date
    Aug 2010
    Location
    Bournemouth, Dorset, UK.
    Posts
    22
    Threads
    2
    Thank You Posts

    Default Adobe PS CS5 plugin to speed file saves

    works by stopping compression so bigger files but if you save a lot as you work and you can compress when your finished

    http://kb2.adobe.com/cps/902/cpsid_90248.html

  2. #2
    Forum Participant
    Join Date
    May 2008
    Location
    Sugar Land, Texas USA
    Posts
    1,819
    Threads
    480
    Thank You Posts

    Default

    Hi Andrew. Never had a problem with CS5 being too slow at saving files, and my typical PSD files are over 100 MB (24MP sensor, layers). My problem is with such large file sizes I need to keep buying external hard-drives. I need a plug-in that makes smaller file sizes, and I'm don't mind if it takes longer to save.
    Also I don't save files until I am finished. Am I supposed to save periodically along the way?
    regards~Bill

  3. #3
    BPN Viewer
    Join Date
    Aug 2010
    Location
    Bournemouth, Dorset, UK.
    Posts
    22
    Threads
    2
    Thank You Posts

    Default Well its all hardware / filesize dependant

    Quote Originally Posted by WIlliam Maroldo View Post
    Hi Andrew. Never had a problem with CS5 being too slow at saving files, and my typical PSD files are over 100 MB (24MP sensor, layers). My problem is with such large file sizes I need to keep buying external hard-drives. I need a plug-in that makes smaller file sizes, and I'm don't mind if it takes longer to save.
    Also I don't save files until I am finished. Am I supposed to save periodically along the way?
    regards~Bill
    If you've stitched panoramas and used layers etc files can get fairly massive (multi GB) and take minutes to save, if like me you save at each stage you save to guard against crashes this can impact on productivity.

  4. #4
    Banned
    Join Date
    Feb 2008
    Location
    Colorado
    Posts
    3,949
    Threads
    254
    Thank You Posts

    Default

    Andrew,

    Disk I/O is usually the slowest operation on a computer system. At a disk write speed of 30 megabytes/second (MB/s), it takes 33 seconds to save 1 gigabyte (GB). But if the file gets compressed, the I/O time decreases. So if you computer is sluggish in this area, is it due to an older system, or memory limited, or slow disk drives? I've seen disk write speeds of 96 MB/s on newer 7200 RPM 6 gigabit/second sata drives (so 1 GByte takes only 10.4 seconds to write) and that was while reading the data from a USB3 disk drive. I just did a test writing to a 3 gbyte/sec 7200 rpm disk from memory and got 5 seconds/gigabyte (199 MB/s transfer rate on an I7 cpu, Ubuntu linux 64-bit OS with 12 GBytes ram). A key to faster performance is lots of ram and a fast (like an I7) cpu. With lots of ram, I/O can be buffered. What this means is that the application starts a write, and the write appears to complete quickly so you can do other stuff while the operating system actually flushes the data to the disk (not sure if windows does this).

    These days there are many cheap computers on the market, and with usually low throughput. We do not need to pay a lot to get very good performance, but one does need to be careful.

    How much ram, what kind of disk interface, and what cpu do you have?

    Roger

  5. #5
    Banned
    Join Date
    Feb 2008
    Location
    Colorado
    Posts
    3,949
    Threads
    254
    Thank You Posts

    Default

    Quote Originally Posted by WIlliam Maroldo View Post
    Hi Andrew. Never had a problem with CS5 being too slow at saving files, and my typical PSD files are over 100 MB (24MP sensor, layers). My problem is with such large file sizes I need to keep buying external hard-drives. I need a plug-in that makes smaller file sizes, and I'm don't mind if it takes longer to save.
    Also I don't save files until I am finished. Am I supposed to save periodically along the way?
    regards~Bill
    I save often. What if there is a power failure (I do have UPS so would have some time to save) or windows crashes, or photoshop crashes? I also save intermediate versions in case I want to go back. E.g. raw file = image1234.cr2, converted = image1234.a.tif, next version image1234.b.psd, then image1234.c.psd until I get to the final, e.g. image1234.d.tif. Whe I'm satisified, I can go back and delete the intermediate files.

    Roger

  6. #6
    Forum Participant
    Join Date
    May 2008
    Location
    Sugar Land, Texas USA
    Posts
    1,819
    Threads
    480
    Thank You Posts

    Default

    Roger; congrats on the elephant picture, very cool! About the subject of this thread. I did say I never had a problem with CS5, and as you have pointed out, the system one uses has alot to do with it. The system I use now (Win 7, 64 bit, 6Gb Ram, i5 processor), and the only one I have used with CS5, has been so stable that I have become complacent about saving. I aslo try to do as much in camera as possible, most adjustment is in ACR, and I don't do much in PS, and if there was a crash I'm only out a few minutes.
    How easily I forget about problems with previous systems, and versions of PS!
    Then I would definitely save more often; I could never tell when I would run out of memory or have system or PS crashes. Again, how easily I forget. regards~Bill

  7. #7
    BPN Viewer
    Join Date
    Aug 2010
    Location
    Bournemouth, Dorset, UK.
    Posts
    22
    Threads
    2
    Thank You Posts

    Default Its for when file sizes necessitate PSB rather than PSD

    Quote Originally Posted by Roger Clark View Post
    Andrew,

    Disk I/O is usually the slowest operation on a computer system. At a disk write speed of 30 megabytes/second (MB/s), it takes 33 seconds to save 1 gigabyte (GB). But if the file gets compressed, the I/O time decreases. So if you computer is sluggish in this area, is it due to an older system, or memory limited, or slow disk drives? I've seen disk write speeds of 96 MB/s on newer 7200 RPM 6 gigabit/second sata drives (so 1 GByte takes only 10.4 seconds to write) and that was while reading the data from a USB3 disk drive. I just did a test writing to a 3 gbyte/sec 7200 rpm disk from memory and got 5 seconds/gigabyte (199 MB/s transfer rate on an I7 cpu, Ubuntu linux 64-bit OS with 12 GBytes ram). A key to faster performance is lots of ram and a fast (like an I7) cpu. With lots of ram, I/O can be buffered. What this means is that the application starts a write, and the write appears to complete quickly so you can do other stuff while the operating system actually flushes the data to the disk (not sure if windows does this).

    These days there are many cheap computers on the market, and with usually low throughput. We do not need to pay a lot to get very good performance, but one does need to be careful.

    How much ram, what kind of disk interface, and what cpu do you have?

    Roger
    It's for when file sizes necesitate PSB rather than PSD (2 GB +), when without the plugin enabled a zip type compression algorithm kicks in, and on macs at least this is single threaded.

    PSB is not something I have to resort to very often, but when I do it has usually involved a lot of work

    Saving large files was the only real bottleneck I had on my MacPro 8 core 12GB Ram with a 4 x 2TB sata II 7200rpm RAiD 0 stripe.

    There are some lab tests here http://macperformanceguide.com/

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Web Analytics