If you want to see this for yourself, here's a sure-fire Lightroom tar baby recipe: There's a bit of a hit to the frame rate, but it's still playable. I've spent a fair bit of time playing Borderlands 2 while Lr grinds away in the background. In fact, if you go open up another program, leaving Lightroom churning away in the background, your new foreground program will be fairly responsive, since Lightroom doesn't use 100% of the computer's resources while it is in such a state. I've seen this on several different computers, both Windows and Mac, which ranged from reasonably fast to positively high-end. ![]() I've seen Lightroom sit there, nearly unresponsive, for a minute or two while it churns through its backlog of work. If you continue pushing Lightroom this way, you can get it to the point where it takes many seconds to apply a keyword. If you restart Lightroom, performance returns. I mean that if you take a pile of photos without any keywords on them and add one or two keywords to each, Lightroom will be noticeably slower after one or two hundred keyword additions. I don't mean lots of keywords on a single photo here. The more keywords you add, the slower Lightroom will get. Here is a catalog of Lightroom keyword failure modes and myths, all culled from my long experience with Lightroom, going back to the pre-1.0 beta days: Heavy keyword use is one of the easiest and most reliable ways to do it. It is not only possible to make Lightroom slow to a crawl, I can do it at will. You can have zillions of keywords in your catalog. ![]() SQLite does have size limits, but they are so high that it simply isn't worth worrying about them. Lightroom uses a SQLite database to hold its keyword information. You can download it to see if it fits for you - it is freeware. It just happens to know well how XnView MP's DB backend is designed vs Lightroom and how is its performance curve. If you want such a thing you can get other DAMs.ĭisclaimer: While I tested other programs from performance POV (AfterShotPro is one of the best, Zoner has a hardcoded upper limit, ACDSee has a rather slow DB, like Lightroom), as I said, I personally use XnView MP together with Photoshop and/or Photivo (an awesome free RAW editor). Rule #3: Lightroom wasn't designed for scalability in mind. ![]() But if you cannot then there are better solutions, but the difference will show up only from several thousands images above.Ĭorollary #2a: If you cannot afford leaving Lightroom be sure to keep your catalogs small. So, Rule #2: In Lightroom try to keep your number of keywords per image low. However, if the cardinality (the number of rows) grows, and this happens quickly if one assigns many keywords to each photo, then the difference in performance increases. Ok, one can argue that it is 33% increase but frankly because the 3rd field is an integer, I don't think that for 100.000-200.000 rows the performance degradation will be so big. This table is very narrow but, again, here Lr choose to have 3 fields instead of 2 (which is the minimum). ![]() But if you cannot then there are other, better solutions.īesides of the keywords table there is another table, the table of keywords assigned to each image. So, Rule #1: In Lightroom try to keep your total number of keywords at minimum. XnView MP which is much faster in these things because it has just one table for keywords and this is almost a half wide (7 fields vs. That said, Lr organizes internally the keywords in several tables which are rather fat (wide - with many fields) in comparison with other programs thing which means that in some situations (queries) it will be (much) slower than other programs. Also, of course, it depends on the hardware on which you're on. It is rather an oblique line and not a stair-like graph. The performance degradation is a quite incremental process. You cannot say that till "n" keywords you won't get any performance degradation and from "n"+1 (ok, "n"+100 or whatever) you suddenly will feel it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |