At Photoshop World this week, performance testing lead Adam Jerugim presented a performance guide with hardware recommendations and information about the CS5 performance preferences. \u00a0I’ve put his notes in this post’s extended entry.<\/p>\n
<\/p>\n
Operating Systems<\/strong>: Mac OS 10.6.4 and Windows 7 64-bit<\/p>\n CPU<\/strong>: Intel Core i7\/Xeon or AMD Phenom II\/Opteron with 4 cores. More than 4 cores gives diminishing\u00a0returns.<\/p>\n<\/p>\n RAM<\/strong>: Enough to keep Efficiency readout at 100%. If Efficiency is low (<95%), adding RAM will provide\u00a0biggest benefit. 4GB will cover most digital photography uses. 8GB leaves room for other apps and fits\u00a0huge documents in RAM.<\/p>\n<\/p>\n Video Card<\/strong>: Any modern card with at least 512MB VRAM; 1GB if doing heavy 3D work.<\/p>\n Disk<\/strong>: Use a separate disk for Photoshop scratch. If you spend a lot of time opening \/ saving large data files,\u00a0another separate disk for data files will speed that up. Faster disks are better. RAID0 is faster. SSD is\u00a0faster yet. RAID0 of SSDs is fastest but super expensive. If you have plenty of RAM (meaning your Efficiency readout is\u00a095% or more), separate\/faster disks for scratch provide minimal benefit. If Efficiency readout is low, a\u00a0separate SSD for Photoshop scratch will be a big win. SSD boot volume will speed booting and app\u00a0launch, but not Photoshop operations.<\/p>\n Memory Usage<\/strong>: this should be no higher than 70%\u00a0on systems running 32bit Photoshop or with less\u00a0than 4GB of total physical RAM. On systems with\u00a08GB or more, use 70% if you plan on running other\u00a0applications at the same time as PS, or higher (up to\u00a090%) if you only plan on using PS on your system.<\/p>\n Efficiency %<\/strong>: can be found in the document window drop-down\u00a0options. Operations fit in RAM when this 95% or greater.<\/p>\n<\/p>\n History & Cache<\/strong>: if you work with small documents\u00a0with lots of layers, start with the Tall and Thin button\u00a0(which will set cache levels = 2, tile size = 128K\/132K). If you work with large documents with few\u00a0layers, try the Big and Flat button (which will set\u00a0cache levels = 6, tile size = 1024K\/1028K). Using\u00a0more history states uses more scratch disk space. \u00a0More history states may also use more RAM,\u00a0particularly when running actions or scripts on large\u00a0documents. If you see Efficiency drop below 95%,\u00a0especially after running actions, try reducing history\u00a0states or adding RAM.<\/p>\n Scratch Disks<\/strong>: a separate drive for Photoshop scratch disk will avoid slowdowns from Photoshop and the OS trying to\u00a0access the disk at the same time. If your Efficiency number often drops below 95%, the gain can be large. Faster disks\u00a0are better. A RAID0 array is faster, an SSD faster still. If using a RAID or SSD, try setting the Tile Size to 1024K \u2013 AMD\u00a0CPUs prefer 132K \/ 1028K sizes, but 128K and especially 1024K are more efficient for RAID and SSD use regardless of\u00a0CPU type.<\/p>\n GPU Settings<\/strong>: you can change GPU settings by clicking on the Advanced Settings button. For more more modern video\u00a0cards there will be three options: Basic, Normal, Advanced. Changes to this setting will only take effect after PS restart,\u00a0and would be worth experimenting with if painting performance is sluggish.<\/p>\n<\/p>\n<\/p><\/p>\n","protected":false},"excerpt":{"rendered":" At Photoshop World this week, performance testing lead Adam Jerugim presented a performance guide with hardware recommendations and information about the CS5 performance preferences. \u00a0I’ve put his notes in this post’s extended entry.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[27],"tags":[],"_links":{"self":[{"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts\/2712"}],"collection":[{"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/comments?post=2712"}],"version-history":[{"count":0,"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts\/2712\/revisions"}],"wp:attachment":[{"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/media?parent=2712"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/categories?post=2712"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/tags?post=2712"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}