<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Optimizing Lightroom for Best Performance: Top Ten Lightroom Speed Tips</title>
	<atom:link href="http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/</link>
	<description>TheLightroomLab.com is for professional and amateur photographers who use Adobe Photoshop Lightroom as part of their digital workflow. We have tips, tricks, tutorials, videos, news, and more.</description>
	<lastBuildDate>Sun, 14 Mar 2010 06:23:57 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ben seelt</title>
		<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/comment-page-2/#comment-7415</link>
		<dc:creator>ben seelt</dc:creator>
		<pubDate>Tue, 24 Nov 2009 14:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://thelightroomlab.com/?p=2250#comment-7415</guid>
		<description>Dear Scott,
Thanks for your very instructive info on woking better in LR.
I am just installing my new Mac. All settings in preferences look o.k., but this happens:
when editing an image to CS4, LR opens the program but does not open the image, saying:
&quot;file could not be opened because CS4 could not be launched&quot;.
I can not get an answer on this matter. Me be you can help me out and save me from starvation.
Kind regard,
Ben.</description>
		<content:encoded><![CDATA[<p>Dear Scott,<br />
Thanks for your very instructive info on woking better in LR.<br />
I am just installing my new Mac. All settings in preferences look o.k., but this happens:<br />
when editing an image to CS4, LR opens the program but does not open the image, saying:<br />
&#8220;file could not be opened because CS4 could not be launched&#8221;.<br />
I can not get an answer on this matter. Me be you can help me out and save me from starvation.<br />
Kind regard,<br />
Ben.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Rouse</title>
		<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/comment-page-2/#comment-7399</link>
		<dc:creator>Scott Rouse</dc:creator>
		<pubDate>Mon, 23 Nov 2009 22:19:59 +0000</pubDate>
		<guid isPermaLink="false">http://thelightroomlab.com/?p=2250#comment-7399</guid>
		<description>Janne,

Thanks for the detailed information.  I really enjoy the &quot;geeky&quot; super-speed tips like this, and I appreciate your input.

-Scott Rouse</description>
		<content:encoded><![CDATA[<p>Janne,</p>
<p>Thanks for the detailed information.  I really enjoy the &#8220;geeky&#8221; super-speed tips like this, and I appreciate your input.</p>
<p>-Scott Rouse</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janne Sjöberg</title>
		<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/comment-page-2/#comment-7398</link>
		<dc:creator>Janne Sjöberg</dc:creator>
		<pubDate>Mon, 23 Nov 2009 21:38:58 +0000</pubDate>
		<guid isPermaLink="false">http://thelightroomlab.com/?p=2250#comment-7398</guid>
		<description>I just wanted to shed some light on the &quot;Keep space on your hard drive&quot; tip. Michael asks if he really needs 400GB free on his 1TB drive, and the answer is yes, if maximum performance is the goal, he does. This is not so much to improve stability (once you have enough free space to write any temporary files, unfragmented, even more free space doesn&#039;t really help you in that regard) but rather because of the way traditional hard drives work. A hard drive’s performance is not consistent across the entire surface, but varies significantly depending on which part of the drive gets read or written. 

Generally, a hard drive will be fastest while writing to the outer edges of the drive’s platters, and performance will decrease when writing closer to the center of the platters. For this reason, drives fill up from the edges toward the center. The specifics of at which points and to what degree performance is cut is drive model-dependant, but generally speaking, the last parts of the disk will have about half the read and write transfer performance of the first parts.  

Typical examples of this can be seen in more detailed tests of hard drives, for instance http://www.tomshardware.com/reviews/2tb-hdd-7200,2430-6.html (just a test of three disks I chose at random to illustrate the point). 
To get the absolute maximum speed from your disk, you shouldn’t normally use much more than 20-25% of the disk, the rest should be unused space. Getting disks that are four times as big as “needed” is expensive, of course, and exactly how much you want to fill your disk, and in other words how much performance degradation you will suffer, will be an individual question. But when you’ve passed  50-60% of your disk space, this starts to be a real factor. 

Finally, this relates to traditional, mechanical hard drives. The story for SSDs is far more complex. While they theoretically don’t suffer any degradation depending on what memory addresses are written, the controllers on current SSDs (especially MLC-based disks) tend to run in to a lot of optimization problems with data writes once free space starts to get scarce. So, expensive as they may be, SSDs will also give you the best performance while they are primarily empty.</description>
		<content:encoded><![CDATA[<p>I just wanted to shed some light on the &#8220;Keep space on your hard drive&#8221; tip. Michael asks if he really needs 400GB free on his 1TB drive, and the answer is yes, if maximum performance is the goal, he does. This is not so much to improve stability (once you have enough free space to write any temporary files, unfragmented, even more free space doesn&#8217;t really help you in that regard) but rather because of the way traditional hard drives work. A hard drive’s performance is not consistent across the entire surface, but varies significantly depending on which part of the drive gets read or written. </p>
<p>Generally, a hard drive will be fastest while writing to the outer edges of the drive’s platters, and performance will decrease when writing closer to the center of the platters. For this reason, drives fill up from the edges toward the center. The specifics of at which points and to what degree performance is cut is drive model-dependant, but generally speaking, the last parts of the disk will have about half the read and write transfer performance of the first parts.  </p>
<p>Typical examples of this can be seen in more detailed tests of hard drives, for instance <a href="http://www.tomshardware.com/reviews/2tb-hdd-7200,2430-6.html" rel="nofollow">http://www.tomshardware.com/reviews/2tb-hdd-7200,2430-6.html</a> (just a test of three disks I chose at random to illustrate the point).<br />
To get the absolute maximum speed from your disk, you shouldn’t normally use much more than 20-25% of the disk, the rest should be unused space. Getting disks that are four times as big as “needed” is expensive, of course, and exactly how much you want to fill your disk, and in other words how much performance degradation you will suffer, will be an individual question. But when you’ve passed  50-60% of your disk space, this starts to be a real factor. </p>
<p>Finally, this relates to traditional, mechanical hard drives. The story for SSDs is far more complex. While they theoretically don’t suffer any degradation depending on what memory addresses are written, the controllers on current SSDs (especially MLC-based disks) tend to run in to a lot of optimization problems with data writes once free space starts to get scarce. So, expensive as they may be, SSDs will also give you the best performance while they are primarily empty.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gregory Wostrel</title>
		<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/comment-page-1/#comment-7367</link>
		<dc:creator>Gregory Wostrel</dc:creator>
		<pubDate>Mon, 23 Nov 2009 04:27:57 +0000</pubDate>
		<guid isPermaLink="false">http://thelightroomlab.com/?p=2250#comment-7367</guid>
		<description>Hi Alison (and others),

I have also found that leaving the XMP writing selected causes a very noticeable performance hit. My simple solution is to leave it off and, when I have finished with a good sized batch of images I select them all in Grid view and hit Command S (just like &quot;Save&quot;) on the Mac or Control S on Windows and LR writes them all then. I look at it like directing LR to generate previews before you start editing. I can walk away and do something else and the XMP files get written.

Greg</description>
		<content:encoded><![CDATA[<p>Hi Alison (and others),</p>
<p>I have also found that leaving the XMP writing selected causes a very noticeable performance hit. My simple solution is to leave it off and, when I have finished with a good sized batch of images I select them all in Grid view and hit Command S (just like &#8220;Save&#8221;) on the Mac or Control S on Windows and LR writes them all then. I look at it like directing LR to generate previews before you start editing. I can walk away and do something else and the XMP files get written.</p>
<p>Greg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alison Shaw</title>
		<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/comment-page-1/#comment-7045</link>
		<dc:creator>Alison Shaw</dc:creator>
		<pubDate>Mon, 16 Nov 2009 16:17:36 +0000</pubDate>
		<guid isPermaLink="false">http://thelightroomlab.com/?p=2250#comment-7045</guid>
		<description>Thank you, David. This makes sense to me about the file size of the TIFFS. I believe we&#039;ve got the quad-core tower, and I know we have an array of fast hard drives, so we&#039;ll up my RAM from my current 4 GB, and look forward to Lightroom 3. And yes, I do have the &quot;Automatically write changes to XMP&quot; switch on.

I&#039;m incredibly appreciative of yours and Scott&#039;s time, thought, expertise, and responsiveness to my Lightroom issues.

Best,
Alison</description>
		<content:encoded><![CDATA[<p>Thank you, David. This makes sense to me about the file size of the TIFFS. I believe we&#8217;ve got the quad-core tower, and I know we have an array of fast hard drives, so we&#8217;ll up my RAM from my current 4 GB, and look forward to Lightroom 3. And yes, I do have the &#8220;Automatically write changes to XMP&#8221; switch on.</p>
<p>I&#8217;m incredibly appreciative of yours and Scott&#8217;s time, thought, expertise, and responsiveness to my Lightroom issues.</p>
<p>Best,<br />
Alison</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/comment-page-1/#comment-7043</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 16 Nov 2009 15:33:58 +0000</pubDate>
		<guid isPermaLink="false">http://thelightroomlab.com/?p=2250#comment-7043</guid>
		<description>Dear Alison,

If I might jump in here.  I think your experiencing the difference in processing time between say a 20 megabyte raw file and a 200 Megabyte tif.  Huge files take more ram and more processing power. Even something as simple as thumbnail generation is going to grow slower as your file sizes grow larger.

Two thoughts:
1.  Stronger hardware.  Ideally, we would want to work with your medium format high-res scans (thats what I am guessing these are) on a quad-core tower with 10+ gigabytes of ram, a 64-bit operating system, and an array of fast hard drives.

2.  Do you have the &quot;Automatically write changes to XMP switch&quot; turned on?  Especially with giant tif / psd files this is always going to make Lightroom slower.  Safer, and more user friendly, but noticeably slower.

I know this doesn&#039;t solve your problems, but perhaps it clears up a little bit of the mystery.  If I may add one more thing-- this is exactly the sort of performance issue that Lightroom 3 should improve.

best wishes,

David</description>
		<content:encoded><![CDATA[<p>Dear Alison,</p>
<p>If I might jump in here.  I think your experiencing the difference in processing time between say a 20 megabyte raw file and a 200 Megabyte tif.  Huge files take more ram and more processing power. Even something as simple as thumbnail generation is going to grow slower as your file sizes grow larger.</p>
<p>Two thoughts:<br />
1.  Stronger hardware.  Ideally, we would want to work with your medium format high-res scans (thats what I am guessing these are) on a quad-core tower with 10+ gigabytes of ram, a 64-bit operating system, and an array of fast hard drives.</p>
<p>2.  Do you have the &#8220;Automatically write changes to XMP switch&#8221; turned on?  Especially with giant tif / psd files this is always going to make Lightroom slower.  Safer, and more user friendly, but noticeably slower.</p>
<p>I know this doesn&#8217;t solve your problems, but perhaps it clears up a little bit of the mystery.  If I may add one more thing&#8211; this is exactly the sort of performance issue that Lightroom 3 should improve.</p>
<p>best wishes,</p>
<p>David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alison Shaw</title>
		<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/comment-page-1/#comment-7041</link>
		<dc:creator>Alison Shaw</dc:creator>
		<pubDate>Mon, 16 Nov 2009 14:57:07 +0000</pubDate>
		<guid isPermaLink="false">http://thelightroomlab.com/?p=2250#comment-7041</guid>
		<description>Hi Scott,

Unfortunately I&#039;m still having &quot;rolling ball&quot; problems, but at least I&#039;ve been able to isolate it, so I&#039;m hoping you might have some further insight. It (this incredible sluggishness) only happens when the images I&#039;m looking at are scanned images rather than digital capture images. Example: if I bring up a folder of 100 images scanned from film, Library Module, Grid View, and then I try and do something so mundane as deleting a keyword, the process might take 15 seconds. Same scenario with a folder of digital capture images displayed on my screen would be 1 second. Any thoughts?

Thanks,
Alison</description>
		<content:encoded><![CDATA[<p>Hi Scott,</p>
<p>Unfortunately I&#8217;m still having &#8220;rolling ball&#8221; problems, but at least I&#8217;ve been able to isolate it, so I&#8217;m hoping you might have some further insight. It (this incredible sluggishness) only happens when the images I&#8217;m looking at are scanned images rather than digital capture images. Example: if I bring up a folder of 100 images scanned from film, Library Module, Grid View, and then I try and do something so mundane as deleting a keyword, the process might take 15 seconds. Same scenario with a folder of digital capture images displayed on my screen would be 1 second. Any thoughts?</p>
<p>Thanks,<br />
Alison</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alison Shaw</title>
		<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/comment-page-1/#comment-6968</link>
		<dc:creator>Alison Shaw</dc:creator>
		<pubDate>Fri, 13 Nov 2009 17:54:56 +0000</pubDate>
		<guid isPermaLink="false">http://thelightroomlab.com/?p=2250#comment-6968</guid>
		<description>Hi Scott,

Thanks again for all of your help, including your email answers to the questions I posed to David.

Best,
Alison</description>
		<content:encoded><![CDATA[<p>Hi Scott,</p>
<p>Thanks again for all of your help, including your email answers to the questions I posed to David.</p>
<p>Best,<br />
Alison</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Holly Suthard</title>
		<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/comment-page-1/#comment-6966</link>
		<dc:creator>Holly Suthard</dc:creator>
		<pubDate>Fri, 13 Nov 2009 17:13:23 +0000</pubDate>
		<guid isPermaLink="false">http://thelightroomlab.com/?p=2250#comment-6966</guid>
		<description>Amazing!! Thank you so much for this tip! I&#039;ve been running LR for two years, even been to a training class, and this has NEVER been mentioned anywhere! MWAH!</description>
		<content:encoded><![CDATA[<p>Amazing!! Thank you so much for this tip! I&#8217;ve been running LR for two years, even been to a training class, and this has NEVER been mentioned anywhere! MWAH!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Rouse</title>
		<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/comment-page-1/#comment-6965</link>
		<dc:creator>Scott Rouse</dc:creator>
		<pubDate>Fri, 13 Nov 2009 17:01:39 +0000</pubDate>
		<guid isPermaLink="false">http://thelightroomlab.com/?p=2250#comment-6965</guid>
		<description>:-)

Thanks, Alison!</description>
		<content:encoded><![CDATA[<p> <img src='http://thelightroomlab.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Thanks, Alison!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alison Shaw</title>
		<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/comment-page-1/#comment-6964</link>
		<dc:creator>Alison Shaw</dc:creator>
		<pubDate>Fri, 13 Nov 2009 16:56:36 +0000</pubDate>
		<guid isPermaLink="false">http://thelightroomlab.com/?p=2250#comment-6964</guid>
		<description>Scott, you&#039;ll have to change your &quot;optimizing-lightroom-for-best-performance-top-ten&quot; to &quot;top-eleven&quot;.........</description>
		<content:encoded><![CDATA[<p>Scott, you&#8217;ll have to change your &#8220;optimizing-lightroom-for-best-performance-top-ten&#8221; to &#8220;top-eleven&#8221;&#8230;&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Rouse</title>
		<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/comment-page-1/#comment-6962</link>
		<dc:creator>Scott Rouse</dc:creator>
		<pubDate>Fri, 13 Nov 2009 16:42:57 +0000</pubDate>
		<guid isPermaLink="false">http://thelightroomlab.com/?p=2250#comment-6962</guid>
		<description>Alison,

Glad we were able to help.

Yes, RAM and &quot;memory&quot; typically mean the same thing in computer terms. With that Mac Pro, you&#039;d probably greatly benefit from increasing the amount of RAM in the machine. It&#039;s something that&#039;s relatively easy to do yourself.

I typically buy aftermarket RAM from &lt;a href=&quot;http://macsales.com&quot; rel=&quot;nofollow&quot;&gt;Other World Computing&lt;/a&gt; or &lt;a href=&quot;http://www.anrdoezrs.net/click-3141040-10674240&quot; rel=&quot;nofollow&quot;&gt;Crucial.com&lt;/a&gt;.

I also sent you an email yesterday answering a few other questions that you&#039;d posed to David. Hope you got it.

Thanks,
Scott</description>
		<content:encoded><![CDATA[<p>Alison,</p>
<p>Glad we were able to help.</p>
<p>Yes, RAM and &#8220;memory&#8221; typically mean the same thing in computer terms. With that Mac Pro, you&#8217;d probably greatly benefit from increasing the amount of RAM in the machine. It&#8217;s something that&#8217;s relatively easy to do yourself.</p>
<p>I typically buy aftermarket RAM from <a href="http://macsales.com" rel="nofollow">Other World Computing</a> or <a href="http://www.anrdoezrs.net/click-3141040-10674240" rel="nofollow">Crucial.com</a>.</p>
<p>I also sent you an email yesterday answering a few other questions that you&#8217;d posed to David. Hope you got it.</p>
<p>Thanks,<br />
Scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alison Shaw</title>
		<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/comment-page-1/#comment-6961</link>
		<dc:creator>Alison Shaw</dc:creator>
		<pubDate>Fri, 13 Nov 2009 16:22:47 +0000</pubDate>
		<guid isPermaLink="false">http://thelightroomlab.com/?p=2250#comment-6961</guid>
		<description>Wow, you have now officially changed life as I currently know it with Lightroom. The un-checking of &quot;open in 32 bit&quot; DRAMATICALLY sped up the program. You have made my day – no, my week.......or even month. Thank you!

FYI, I have 4GB of &quot;Memory&quot; – I&#039;m assuming that&#039;s RAM?</description>
		<content:encoded><![CDATA[<p>Wow, you have now officially changed life as I currently know it with Lightroom. The un-checking of &#8220;open in 32 bit&#8221; DRAMATICALLY sped up the program. You have made my day – no, my week&#8230;&#8230;.or even month. Thank you!</p>
<p>FYI, I have 4GB of &#8220;Memory&#8221; – I&#8217;m assuming that&#8217;s RAM?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Rouse</title>
		<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/comment-page-1/#comment-6947</link>
		<dc:creator>Scott Rouse</dc:creator>
		<pubDate>Thu, 12 Nov 2009 22:07:13 +0000</pubDate>
		<guid isPermaLink="false">http://thelightroomlab.com/?p=2250#comment-6947</guid>
		<description>Alison,

I know that&#039;s really frustrating. How much RAM do you have in your Mac Pro?

Are you running Lightroom in 64-bit mode? Find Lightroom in the Applications Folder, right-click on it and choose &quot;Get Info.&quot; If the &quot;Open in 32-bit mode&quot; box it checked, uncheck it. Restart Lightroom and see if that makes any difference for you.

-Scott</description>
		<content:encoded><![CDATA[<p>Alison,</p>
<p>I know that&#8217;s really frustrating. How much RAM do you have in your Mac Pro?</p>
<p>Are you running Lightroom in 64-bit mode? Find Lightroom in the Applications Folder, right-click on it and choose &#8220;Get Info.&#8221; If the &#8220;Open in 32-bit mode&#8221; box it checked, uncheck it. Restart Lightroom and see if that makes any difference for you.</p>
<p>-Scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alison Shaw</title>
		<link>http://thelightroomlab.com/2009/07/optimizing-lightroom-for-best-performance-top-ten-lightroom-speed-tips/comment-page-1/#comment-6945</link>
		<dc:creator>Alison Shaw</dc:creator>
		<pubDate>Thu, 12 Nov 2009 21:47:04 +0000</pubDate>
		<guid isPermaLink="false">http://thelightroomlab.com/?p=2250#comment-6945</guid>
		<description>I&#039;ve done pretty much everything you&#039;ve mentioned on your Optimizing Lightroom for Best Performance list, but still my Lightroom is slow as molasses. My Lightroom performance has not always been this way. I&#039;ve got a MacPro with 400GB of available space. I&#039;ve got 30,000 images in a single catalog. The rolling ball is driving me crazy........</description>
		<content:encoded><![CDATA[<p>I&#8217;ve done pretty much everything you&#8217;ve mentioned on your Optimizing Lightroom for Best Performance list, but still my Lightroom is slow as molasses. My Lightroom performance has not always been this way. I&#8217;ve got a MacPro with 400GB of available space. I&#8217;ve got 30,000 images in a single catalog. The rolling ball is driving me crazy&#8230;&#8230;..</p>
]]></content:encoded>
	</item>
</channel>
</rss>
