Examining LR 4.x performance using Sysinternals ProcessMonitor

has adobe looked @ lr 4.x performance using sysinternals processmonitor?  feel can give tremendous insight application doing "under covers" without running inside of debugger.

 

i'm providing 2 example captures, both in excel format:

 

---------------------------

1) lightroom sitting idle (i haven't touched lr couple of minutes before capturing information).  if remember right, maybe 30 seconds worth of activity coming lightroom.

click link download: http://dl.dropbox.com/u/19756227/lightroom/lightroom%20idle%20logfile.xlsx

 

2) before starting capture here, lr had been sitting idle time. started capture. clicked new image (file name = 20120825_2470.cr2), activated crop tool, deactivated crop tool, ended capture. 10 or 11 seconds worth of capture time.

click link download: http://dl.dropbox.com/u/19756227/lightroom/lightroom%20activate%20crop%20tool%20logfile.xl sx

---------------------------

 

capture #1 meant give idea "background noise" ... meaning, capture of lightroom doing when not servicing ui.

capture #2 meant show how long takes load image activate , deactivate crop tool (this in develop module).

 

this lightroom 4.2rc running on 3rd generation core i7-2860qm (2.5ghz) 16gb of memory on win7-64 images on local hard drive (c drive) , catalog , previews residing on ssd (d drive).

 

some interesting things note...

- how opens dell u3011.icm monitor profile , how time spent there. (hint: lot more once - , wonder why didn't read file once on startup , done it?)

 

- how opens cameraraw\defaults\preferences.xmp file (again, lot more once - why not load once @ start up?)

 

- see lot of activity happening on file on hard drive (c:\users\dwterry\appdata\local\temp\etilqs_mgzwz6ai0qswbho) , i'm wondering if there way tell lightroom store such files on ssd instead? catalog stored on ssd, if lightroom use path of catalog determine create these local temp files, allow me optimize system performance way.

 

- see lots of activity reading image (file name referenced above). figure that's part of normal activity. read file in 64k @ time. makes sense.

 

- see xmp file being updated , wonder why? haven't changed yet. did click on image, activate , deactivate crop tool without doing anything. optimize write .xmp file when changes.

 

- see majority of time being spent creating , closing threads. that's real work happens. wonder if threads optimized?

 

anyway... that's bit of insight little tool used monitor process.  wonder if adobe engineers (people real access source code , debuggers) check out , see if can find ways optimize lightroom doing?

 

this brand new machine. it's faster previous computer. upgraded try work around lr 4.x sluggishness. lr 4.2 still slower 3.6 on old computer. goal here try identify problem cure can found.

download sysinternals processmonitor tool directly microsoft here:
http://technet.microsoft.com/en-us/sysinternals/bb896645

More discussions in Lightroom Classic CC

adobe