The database optimization/check operation acts ONLY on the SQLlite database... it's doing a consistency checksum and other validation. It does nothing else regards the previews and rendering issues. Whatever LR is doing regards previews, etc, is unconnected with the database consistency optimization/check.
Lightroom is a heavily threaded application, complex. I opened up some performance analysis tools and watched it while I did a few common things. At one point, up to sixty threads were busy on various operations simultaneously. I selects forty files and told it to build 1:1 previews ... In the background right now, there are about about thirty threads running and doing significant work. It just got finished ... back down to about 12 threads, only one of which is clocking activity at a minimal rate. The most I've seen it consume in physical RAM is 1.6G, when I told it to apply a set of Develop edits to about 200 files. Running it in a 2G system could be a little tight, depending upon what else you are using simultaneously as it can push up the paging and cause various fits and starts. I run it on a Power Mac G5 2.0Ghz DP system with 3G RAM and a fast hard drive system, where performance is pretty darn smooth. Godfrey On Oct 7, 2007, at 3:08 PM, Igor Roshchin wrote: > > Indeed, I did not find any memory/swap file management in LR. > As for the computer memory, - this computer has 2GB physical memory > and I don't see the system hitting it while LR is working. > Somehow, it is indeed related to LR doing something of its own > in the first 2-5-10-15 minutes.. It is somewhat wierd, taking into > account that sometimes it may be immediately following the > optimization > of its database, and that it doesn't happen everytime I start LR. -- PDML Pentax-Discuss Mail List [email protected] http://pdml.net/mailman/listinfo/pdml_pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
