var advanced_ads_pro_visitor_conditions = {"referrer_cookie_name":"advanced_ads_pro_visitor_referrer","referrer_exdays":"365","page_impr_cookie_name":"advanced_ads_page_impressions","page_impr_exdays":"3650"};
var essb_settings = {"ajax_url":"https:\/\/www.lightstalking.com\/wp-admin\/admin-ajax.php","essb3_nonce":"b59c54b5e1","essb3_plugin_url":"https:\/\/www.lightstalking.com\/wp-content\/plugins\/easy-social-share-buttons3","essb3_stats":true,"essb3_ga":false,"essb3_ga_ntg":false,"blog_url":"https:\/\/www.lightstalking.com\/","post_id":"259701"};
Lightroom is a great tool, possibly the best on the market at the moment. However, Adobe has that bad habit of not properly setting up their software by default, so you have to do it on your own in order to get the most out of it. Lightroom is no exception in this matter.
This means your workflow can slow down because Lightroom is struggling to keep up with everyday demands. Fear not, we have some excellent tips coming your way to help fix that.
When you start using it, it will work great, quick and responsive, but as time passes by, it will get slower, even to the point of being annoying. This is mostly due to the way one uses Lightroom, but also because of the way it is set up.
Ideal Hardware For Optimal Performance
Lightroom, for the most part, relies on CPU, drive access, and RAM. From the tests I’ve done, slower 4 core CPUs will perform better than faster 2 core CPU, so make sure you have a 4 core processor to make the most of Lightroom.
When comparing Lightroom between an i5 4570K working on around 4GHZ (when overclocked), to 6 core i7 processors, or even 8 core AMD processors, there wasn’t much of a difference.
This means that Lightroom is getting diminishing returns after a certain point of processing power, or there is a bottleneck somewhere else in the system (possibly drive access time).
Current setup that I'm running. The only addition I would make is a bigger and faster SSD.
With the resolutions constantly increasing, Lightroom also needs more RAM. Just a year ago I was working with 8GB RAM installed on my PC, and then Lightroom used all of it.
Since I’ve upgraded to 32GB of RAM, which wasn’t such an expensive investment, I’ve noticed that for my workflow (importing around 1000 photos, picking through them, editing them, stitching a few panoramas and a few HDR’s) the RAM usage by Lightroom alone goes up to 24-26 GB on average!
The OS needs a bit of RAM too, which will get you to around 28-30GB of used RAM. It is nice to have a couple of GB of unused RAM, so the OS can smoothly do the swaps and dumps and such.
The biggest speed gain was from an SSD. It is funny that I am using an inexpensive Kingston SSD and it made a huge difference moving the catalog from the quite fast Western Digital RED disk drive. But that is to be expected. There will probably be quite a good boost the faster the SSD is.
How Large Is Your Camera RAW Cache Size
No matter how fast your hardware is, however, Lightroom will find a way to slow down for some reason. Many users, including me, found a great increase in speed afterincreasing the Camera RAW cache size.
It defaults somewhere around 2GB. Increase it to 20GB or even more (but make sure that amount doesn’t exceed the free space on your main drive) and you’ll notice the difference in speed right away.
You can find this setting in Edit -> Preferences -> File Handling.
Thinking of upgrading your Lightroom skills? Well, now that you've done what you can to ensure it;s running as efficiently as possible, have a peek at this amazing tutorial series “Lightroom Made Easy“. You'll come away having learned some fantastic tips the pros use to produce the kind of images you've always wanted. This training works across all versions from 3 thru 6/CC.
Smaller Catalogs
Just until recently, I had one catalog for all my work. Although not having to switch catalogs to dig through the archive is quite convenient, and having a large catalog reduces the startup time of Lightroom, it increases the risk of losing your edits (imagine a drive having a few bad sectors or dead cells and the catalog is rendered useless).
Mainly it slows down the edits. Having I’ve chopped up my main catalog, to one catalog per year, the increase in speed was quite welcome.
Turn Off “Automatically Write Changes Into XMP”
This feature is located in the “Catalog Settings” menu in Lightroom. It can be accessed by the following path: Edit -> Preferences -> General -> Go To Catalog Settings and then choose File Handling in the new window that opens.
What does it do?
It creates redundant XMP files which store the edits, instead of being stored in the Catalog itself. This makes all the edits slower, and Lightroom might not utilize the XMP files properly. It is basically an outdated way of storing the edits.
Using Your Graphics Card
When Adobe updated Lightroom to version 6, it introduced the ability to do the processing with the aid of a graphics card. However, that feature turned out to be quite tricky.
Certain CPU and GPU combinations prove to be slower than just using the CPU to do all the work. Therefore, test out this feature, and see if it is a performance gain, or a bottleneck.
At the beginning for me it turned out to be slower, since the GPU needed some time to react and do the edit, but now it is slightly faster than using the CPU only. I suppose with the newer versions of Lightroom and newer drivers for the GPU the issues are getting polished out.
Ditch Your JPEG Copies
If you are shooting RAW + JPEG and you have no strict need for the JPEG images, so just switch to RAW only.
The additional JPEG copy of the image, is not only redundant, but it also slows down Lightroom (since it has to register twice the amount of photos in the catalog), and it clogs up your drive (the more files, the slower the access times get).
Defragmenting Disk Drives
Often it doesn’t make a difference, and newer versions of Windows are quite efficient in placing files without much fragmentation. But just in case, run Disk Defragmentation once in awhile.
Thinking of upgrading your Lightroom skills? Well, now that you've done what you can to ensure it;s running as efficiently as possible, have a peek at this amazing tutorial series “Lightroom Made Easy“.
You'll come away having learned some fantastic tips the pros use to produce the kind of images you've always wanted. This training works across all versions from 3 thru 6/CC.
I am not sure the advice to turn off write to XMP is the right choice. Storing everything in the catalogue means if you loose the catalogue you loose the edits. Writing to XMP means in the worst case you can create your catalogue again.
I think the same. XMP files is not only a backup security of some sort, it also allows other programs to access or modify the files as desired. Photoshop opens them in ACR with the correct settings and sometimes I use Photo Mechanic to browse and select the files, due to its unprecedented speed. Itmodifies the XMP and LR just reads the update.
The amount of RAM used by LR is not that straight forward. If I understand correctly then from Windows 7 onwards, Windows will assign as much memory to applications as is available (or close to that). It might thus assign 26Gb but 8Gb would produce the same or very similar results.
Note, if you are using an SSD, defray is likely a mistake. Almost all SSD drives have a feature known as wear leveling which intentionally shifts data around to avoid rewriting the same flash memory too many times and causing premature death. As such defrag will accomplish nothing but further wear on your disk.
“Lightroom, for the most part, relies on CPU, drive access, and RAM”.
Well, duh – I’d never have guessed that! 😉
I have 16mb ram 2 hds the c ssd drive has the catalog and lightroom using 257gb of 931 gb but all my dng,s raw,s are on the d conventional drive 463 gb used of 1.3 tb am i taking a big hit on performance or is this a reasonable configuration thanks for the post
var advanced_ads_cookies = {"cookie_path":"\/","cookie_domain":""};
var advadsCfpInfo = {"cfpExpHours":"3","cfpClickLimit":"3","cfpBan":"7","cfpPath":"","cfpDomain":"www.lightstalking.com"};
var beloadmore = {"url":"https:\/\/www.lightstalking.com\/wp-admin\/admin-ajax.php","query":{"post__not_in":[259701],"category_name":"lightroom","posts_per_page":3}};
var tve_dash_front = {"ajaxurl":"https:\/\/www.lightstalking.com\/wp-admin\/admin-ajax.php","force_ajax_send":"1","is_crawler":"","recaptcha":[],"post_id":"259701"};
var TVE_Ult_Data = {"ajaxurl":"https:\/\/www.lightstalking.com\/wp-admin\/admin-ajax.php","ajax_load_action":"tve_ult_ajax_load","conversion_events_action":"tve_ult_conversion_event","shortcode_campaign_ids":[],"matched_display_settings":[],"campaign_ids":[],"post_id":259701,"is_singular":true,"tu_em":"","evergreen_redirects":[]};
(function() { var po = document.createElement('script'); po.type = 'text/javascript'; po.async=true;; po.src = 'https://www.lightstalking.com/wp-content/plugins/easy-social-share-buttons3/lib/modules/conversions-pro/assets/share-conversions-tracker.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(po, s); })();(function() { var po = document.createElement('script'); po.type = 'text/javascript'; po.async=true;; po.src = 'https://www.lightstalking.com/wp-content/plugins/easy-social-share-buttons3/assets/modules/pinterest-pro.min.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(po, s); })();(function() { var po = document.createElement('script'); po.type = 'text/javascript'; po.async=true;; po.src = 'https://www.lightstalking.com/wp-content/plugins/easy-social-share-buttons3/assets/modules/subscribe-forms.min.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(po, s); })();(function() { var po = document.createElement('script'); po.type = 'text/javascript'; po.async=true;; po.src = 'https://www.lightstalking.com/wp-content/plugins/easy-social-share-buttons3/assets/js/essb-core.min.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(po, s); })();
var essb_handle_stats = function(oService, oPostID, oInstance) { var element = jQuery('.essb_'+oInstance); var instance_postion = jQuery(element).attr("data-essb-position") || ""; var instance_template = jQuery(element).attr("data-essb-template") || ""; var instance_button = jQuery(element).attr("data-essb-button-style") || ""; var instance_counters = jQuery(element).hasClass("essb_counters") ? true : false; var instance_nostats = jQuery(element).hasClass("essb_nostats") ? true : false; if (instance_nostats) { return; } var instance_mobile = false; if( (/Android|webOS|iPhone|iPad|iPod|BlackBerry|IEMobile|Opera Mini/i).test(navigator.userAgent) ) { instance_mobile = true; } if (typeof(essb_settings) != "undefined") { jQuery.post(essb_settings.ajax_url, { 'action': 'essb_stat_log', 'post_id': oPostID, 'service': oService, 'template': instance_template, 'mobile': instance_mobile, 'position': instance_postion, 'button': instance_button, 'counter': instance_counters, 'nonce': essb_settings.essb3_nonce }, function (data) { if (data) { }},'json'); } }; var essb_log_stats_only = function(service, postId, position) { var instance_mobile = false; if( (/Android|webOS|iPhone|iPad|iPod|BlackBerry|IEMobile|Opera Mini/i).test(navigator.userAgent) ) { instance_mobile = true; } if (typeof(essb_settings) != "undefined") { jQuery.post(essb_settings.ajax_url, { 'action': 'essb_stat_log', 'post_id': postId, 'service': service, 'template': position, 'mobile': instance_mobile, 'position': position, 'button': position, 'counter': false, 'nonce': essb_settings.essb3_nonce }, function (data) { if (data) { }},'json'); } };
let ccwpDOMLoaded=!1;
let ccwp_loaded = false;
let resources_length=0;
let resources =undefined;
let is_last_resource = 0;
ccwpUserInteractions=["keydown","mousemove","wheel","touchmove","touchstart","touchend","touchcancel","touchforcechange"];
ccwpUserInteractions.forEach(function(e){
window.addEventListener(e,calculate_load_times);
});
function calculate_load_times() {
// Check performance support
if (performance === undefined) {
console.log("Performance NOT supported");
return;
}
// Get a list of "resource" performance entries
resources = performance.getEntriesByType("resource");
if (resources === undefined || resources.length <= 0) {
console.log("NO Resource performance records");
}
if(resources.length){
resources_length=resources.length;
}
for(let i=0; i < resources.length; i++) {
if(resources[i].responseEnd>0){
is_last_resource = is_last_resource + 1;
}
}
let uag = navigator.userAgent;
let gpat = /Google Page Speed Insights/gm;
let gres = uag.match(gpat);
let cpat = /Chrome-Lighthouse/gm;
let cres = uag.match(cpat);
let wait_till=300;
let new_ua = "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36";
let new_ua2 = "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36";
if(gres || cres || uag==new_ua || uag==new_ua2){
wait_till = 3000;
}
if(is_last_resource==resources.length){
setTimeout(function(){
console.log("ccwpTriggerDelayedScripts timeout : "+wait_till);
ccwpTriggerDelayedScripts();
},wait_till);
}
}
window.addEventListener("load", function(e) {
console.log("load complete");
setTimeout(function(){
calculate_load_times();
},100);
});async function ccwpTriggerDelayedScripts() {
if(ccwp_loaded){ return ;}
ccwpPreloadStyles();
ccwpPreloadDelayedScripts();
ccwpLoadCss();
ccwpScriptLoading();
ccwp_loaded=true;
}
function ccwpPreloadStyles() {
let e = document.createDocumentFragment();
var cssEle = document.querySelectorAll("link[rel=ccwpdelayedstyle]");
for(let i=0; i <= cssEle.length;i++){
if(cssEle[i]){
cssEle[i].href = removeVersionFromLink(cssEle[i].href);
let r = document.createElement("link");
r.href = cssEle[i].href;
r.rel = "preload";
r.as = "style";
e.appendChild(r);
}
}
document.head.appendChild(e);
}
function ccwpPreloadDelayedScripts() {
var e = document.createDocumentFragment();
document.querySelectorAll("script[type=ccwpdelayedscript]").forEach(function(t) {
var n = removeVersionFromLink(t.getAttribute("src"));
if (n) {
t.setAttribute("src", n);
var r = document.createElement("link");
r.href = n, r.rel = "preload", r.as = "script", e.appendChild(r)
}
}), document.head.appendChild(e)
}
function ccwpScriptLoading(){
var jsEle = document.querySelectorAll("script[type=ccwpdelayedscript]");
jsEle.forEach(function(t) {
t.type = "text/javascript";
if(t.src)
{
t.src = removeVersionFromLink(t.src);
}
});
}function ccwpLoadCss(){
var cssEle = document.querySelectorAll("link[rel=ccwpdelayedstyle]");
for(let i=0; i <= cssEle.length;i++){
if(cssEle[i]){
cssEle[i].href = removeVersionFromLink(cssEle[i].href);
cssEle[i].rel = "stylesheet";
cssEle[i].type = "text/css";
}
}var cssEle = document.querySelectorAll("style[type=ccwpdelayedstyle]");
for(let i=0; i <= cssEle.length;i++){
if(cssEle[i]){
cssEle[i].type = "text/css";
}
}
}
function removeVersionFromLink(link)
{
if(ccwpIsValidUrl(link))
{
const url = new URL(ccwpFormatLink(link));
url.searchParams.delete("ver");
url.searchParams.delete("time");
return url.href;
}
else{
return link;
}
}
function ccwpIsValidUrl(urlString)
{
if(urlString){
var expression =/[-a-zA-Z0-9@:%_\+.~#?&//=]{2,256}\.[a-z]{2,4}\b(\/[-a-zA-Z0-9@:%_\+.~#?&//=]*)?/gi;
var regex = new RegExp(expression);
return urlString.match(regex);
}
return false;
}
function ccwpFormatLink(link)
{
let http_check=link.match("http:");
let https_check=link.match("https:");
if(!http_check && !https_check)
{
return location.protocol+link;
}
return link;
}
6 Comments
I am not sure the advice to turn off write to XMP is the right choice. Storing everything in the catalogue means if you loose the catalogue you loose the edits. Writing to XMP means in the worst case you can create your catalogue again.
I think the same. XMP files is not only a backup security of some sort, it also allows other programs to access or modify the files as desired. Photoshop opens them in ACR with the correct settings and sometimes I use Photo Mechanic to browse and select the files, due to its unprecedented speed. Itmodifies the XMP and LR just reads the update.
The amount of RAM used by LR is not that straight forward. If I understand correctly then from Windows 7 onwards, Windows will assign as much memory to applications as is available (or close to that). It might thus assign 26Gb but 8Gb would produce the same or very similar results.
Note, if you are using an SSD, defray is likely a mistake. Almost all SSD drives have a feature known as wear leveling which intentionally shifts data around to avoid rewriting the same flash memory too many times and causing premature death. As such defrag will accomplish nothing but further wear on your disk.
“Lightroom, for the most part, relies on CPU, drive access, and RAM”.
Well, duh – I’d never have guessed that! 😉
I have 16mb ram 2 hds the c ssd drive has the catalog and lightroom using 257gb of 931 gb but all my dng,s raw,s are on the d conventional drive 463 gb used of 1.3 tb am i taking a big hit on performance or is this a reasonable configuration thanks for the post