Непонятно почему катастрофически снизилась скорость работы Lightroom'а. Изображение в режиме Develop грузятся по 2-3 минуты, экспорт одной фотографии занимает минут 5: полоска экспорта в левом углу появляется, но движется так медленно, что возникает ощущение, что программа зависла. Аналогично работают и другие функции -- импорт, загрузка превьюшек в режиме library и т.п. С мощностью компьютера это не связано -- ещё пару дней назад проблем не было.
Не помогает ни очистка кэша, ни удаление каталогов prewiew, ни переустановка, ни даже установка более свежей 2.0 (сейчас у меня 1.4.1). Саму базу удалять не хочется. Можно ли как-то по-другому справиться с ситуацией?
Lightroom стал работать медленно
Всего 22 сообщ.
|
Показаны 1 - 20
Lightroom стал работать медленно
Re[Дмитрий Кудинов]:
раньше проблема была при накоплении в базе большого количества фотографий...
для себя решил её разбивая фотографии на каталоги по годам
в 2.0 возможно есть какие-то оптимизации, но хто их знает...
для себя решил её разбивая фотографии на каталоги по годам
в 2.0 возможно есть какие-то оптимизации, но хто их знает...
Re[Качанов Александр]:
Делаю так же. Хотя общее количество фотографий относительно большое (около 1500 штук), они разбиты на каталоги по 100-150 штук. Причём фотографии подгружаются с места их размещения.
Re[Дмитрий Кудинов]:
У вас это только с Lightroom илидругие приложения тоже тормозят?
Re[Самарец]:
Только с Лайтрум, остальное нормально работает.
Re[Дмитрий Кудинов]:
от: Дмитрий Кудинов
Делаю так же. Хотя общее количество фотографий относительно большое (около 1500 штук), они разбиты на каталоги по 100-150 штук. Причём фотографии подгружаются с места их размещения.
это называется большое?
у меня где-то двадцать тысяч,
причем равы лежат в папках где-то по 1000.
просто вторая версия более ресурсоемкая.
это очевидный факт :(
Re[шыбека]:
Так и 1-ая не работает ;(
Re[Дмитрий Кудинов]:
[quot]Непонятно почему катастрофически снизилась скорость работы Lightroom'а. Изображение в режиме Develop грузятся по 2-3 минуты[/quot]
Проверил только-что в ражиме Develop 5 секунд в режиме просмотра 2 секунд. Стоит 2 последняя версия, 1.4 работала чуть медленней, но не значительно, в базе около 3000 фоток. В чем у вас причина сказать не могу, вероятно в ПК одна из причин возможно памяти мало.
Проверил только-что в ражиме Develop 5 секунд в режиме просмотра 2 секунд. Стоит 2 последняя версия, 1.4 работала чуть медленней, но не значительно, в базе около 3000 фоток. В чем у вас причина сказать не могу, вероятно в ПК одна из причин возможно памяти мало.
Re[vgm]:
Проблема решилась переносом каталога Лайтрума в другое место на диске.
Re[Дмитрий Кудинов]:
а где он у вас, простите, лежал?
на другой физический диск перенесли?
дефрагментировали?
лично у меня вторая версия подхватила каталог первой,
но именно что медленнее...
:(
на другой физический диск перенесли?
дефрагментировали?
лично у меня вторая версия подхватила каталог первой,
но именно что медленнее...
:(
Re[Дмитрий Кудинов]:
от: Дмитрий Кудинов
Делаю так же. Хотя общее количество фотографий относительно большое (около 1500 штук), они разбиты на каталоги по 100-150 штук. Причём фотографии подгружаются с места их размещения.
Ерунда.
У меня одна сессия была 1500. Общее число фотографий в Лайтрум - намного больше.
Нормально Лайтрум работает по скорости.
Если старая версия - рекомендуется обновить до последней 1.4.1 - он заметно шустрее.
Re[шыбека]:
Перенёс на другой логический диск, который в отличие от основного почти пустой. Это помогло.
Re[Дмитрий Кудинов]:
от: Дмитрий Кудинов
Перенёс на другой логический диск, который в отличие от основного, почти пустой. Это помогло.
Тады бы простая дефрагментация основного помогла бы не хуже переноса.
Re[Дык]:
Не так давно тоже сталкнулся с аналогичной ситуацией — чрезвычайно медленная работа всего, вплоть до просто включения. Версия 1.4.1. Рестарт софта, компа, оптимизация каталога, переустановка, откат не помогли. А на следующий день все нормализовалось.. Но переодически начинается вновь, и так же внезапно заканчивается. Выхожу из ситуации перегружаясь в параллельно стоящий хакинтош и работая с тем же каталогом там)))) (НО! Сразу, баги начались ДО хокинтоша)))
Re[Дмитрий Кудинов]:
Попробуйте создать новый каталог, импортировав часть фотографий из старого.
У меня каждый каталог (это не директория а термин лайтрума который означает не только отдельную директорию но и отдельную базу) это год. 2007 2008
В конце года, когда фото набирается не один десяток тысяч, у меня тоже начинает подтормаживать =)
Фотограф Игорь Алексеев
У меня каждый каталог (это не директория а термин лайтрума который означает не только отдельную директорию но и отдельную базу) это год. 2007 2008
В конце года, когда фото набирается не один десяток тысяч, у меня тоже начинает подтормаживать =)
Фотограф Игорь Алексеев
Re[Дмитрий Кудинов]:
А подскажите, как разбить один большой каталог на пару маленьких?
Re[Дмитрий Кудинов]:
Hurry up Lightroom! Speed Tips!
by Victoria Bampton, originally posted on DWF
[Warning - this is quite long. I had originally intended to split it over a number of blog posts, but it'll be easier to reference as one post. It's on my blog, but I thought I'd post it here as it may come in handy.]
Who has never said "hurry up Lightroom"? Speed is one of the most popular feature requests from Lightroom users everywhere, and no doubt the engineers will continue working on Lightroom's performance over time, but for now, there are plenty of things you can do yourself. Some are obvious, some not so…
Speed Tips in Library module
There's a big difference between rendering previews that have never been built or that need updating, and loading those ready-built previews from disc. How can you tell the difference? The overlay in Loupe view will tell you exactly what it's doing - and therefore what you can do to help.
"Rendering Preview…" means it's rendering a preview for the first time - and you're having to wait for it! You could set Lightroom rendering the previews when it imports, by selecting your chosen preview size in the import dialog - it'll slow you down initially but once it finishes rendering, it'll be much quicker. For files that are already in your catalog, select them all in Grid view and go to Library menu > Previews > Render Standard Previews or Render 1:1 Previews, and go off and leave it until it's finished. It'll skip any that already have current previews, and you'll find browsing much quicker when it's finished.
So what size previews should you render? If you want to quickly zoom into 1:1 view in the Library module (not Develop), then it's a no-brainer - render 1:1 previews rather than Standard-Sized previews, either in the Import dialog or using the menu command noted above. On the other hand, if you rarely zoom in Library module, you're better off using Standard-Sized previews, as they'll take up less disc space and be quicker to read from the cache.
If you see the "Rendering: Higher Quality…" overlay, it means the existing preview is too small or too low quality. If you're seeing that overlay in Fit or Fill view, you'll want to reconsider your Standard preview size. You'll find those settings in the Catalog Settings dialog under the Edit menu (Windows) / Lightroom menu (Mac). Generally speaking the Medium quality setting is fine, but you may decide to increase the Standard preview size from 1440 to a larger size if you have a high resolution screen and regularly see the "Rendering: Higher Quality…" overlay.
"Rendering: File Changed…" means, well, that's the file's changed since the preview was created. That could mean that you've made changes in the Develop module, using the Quick Develop panel, or by applying a preset. Using the Render Standard Preview menu command to update those previews while you do something else will speed up your browsing.
"Loading from Previews…" is the overlay you're aiming for - that means your existing preview is being loaded from the preview cache, which is the quickest option.
Speed Tips in Develop module (or making Quick Develop changes in Library)
First, you need to understand the difference between Library module and Develop module. Library shows you lower quality previews from the previews cache. Develop, on the other hand, assumes you need an accurate view, so it first shows you the preview from the preview cache, then does a quick read of the raw file, frees up the sliders for you to start working, and then finishes loading properly, before it turns off the "Loading…" overlay. You don't have to wait for the overlay to disappear before starting work on the image - and if you find it distracting, you can turn it off in the View menu > View Options > Loupe panel > 'Show message when loading or rendering photos'.
That's all well and good, but that's still a lot of raw data to load and process each time you switch images. Have you ever noticed, though, that when you adjust a file in Develop, move to another image, and then come back to that first image again, it loads much quicker than it did the first time? That's where the Camera Raw cache, also known as the ACR cache, comes in. When Lightroom reads the data the first time, it adds it into the shared Camera Raw cache. When you load that image into Develop module, where possible, it will load that cached data, which is much quicker than reading and processing the original raw file data.
By default, that Camera Raw cache is only 1gb in size, and when new data gets added, the oldest data is removed. With only 1gb of space, that happens quite quickly, so you're not seeing the benefit. If you go to Lightroom's Preferences dialog, and look in the File Handling tab, you can change the cache size to suit - up to a maximum of 50gb. Bigger is better! You can also change the location if you wish to - but make sure it's on a fast hard drive.
Once that data is cached, it's much faster moving between images in the Develop modules - almost instantaneous on high end machines. Of course, that is only helpful when Lightroom has recently read the raw file, and added it to the cache - and there isn't currently a menu command to pre-load the Camera Raw cache. All is not lost!
There's a trick to pre-loading the Camera Raw cache - in addition to actually viewing the image in Develop module, there's another obvious time when Lightroom has to read (and therefore caches) the raw data - namely, when rendering previews. If you haven't already rendered previews for your files, simply using the Library menu > Render Standard-Sized Previews command will do the trick. If, however, you already have current previews, you can force them to re-render by making a minor or reversible change to the images (i.e. by using a Quick Develop button) and then using the Render Standard-Sized Previews menu command. Leave it to finish, and by the time you come back, even the Develop module should be moving through the images at a much more comfortable speed.
Dispelling the Catalog Myths
It's true that large catalogs can be a little slower than small catalogs - but we are talking BIG catalogs. It's not generally a good reason (any more) to split your library into 300 different catalogs - that just defeats the object of having a DAM system like Lightroom.
If you find Lightroom is feeling a little sluggish, find the Catalog Settings dialog under the Edit menu (Windows) / Lightroom menu (Mac), and press the "Relaunch and Optimize" button to perform database optimization. It's worth doing regularly, and any time you make significant database changes like importing or removing large numbers of files.
Finally, Hardware Tips & OS Tweaks
There is no question, Lightroom loves good hardware, but it can still run nicely on older systems too. Do make sure you're running the latest Lightroom release (currently 2.3) as performance improvements have been made to each release.
The system requirements are listed as Intel Pentium 4 or equivalent (i.e. a processor with the SSE2 instruction set or later), with 1gb of RAM and 1gb of hard drive space. Now let's be clear - those are minimum system requirements. It'll run - well, it'll walk! But if you start trying to feed 5d Mk2 files into Lightroom with a computer that was in the Ark, don't expect it to be fast, and don't complain about the speed. If you're going to spend money on the latest and greatest cameras, bear in mind that your computer hardware may also require a helping hand with those new super-size files. Yes, even those sRAW files. ;-)
If you're working with existing hardware, check your graphics card. You don't need a heavy-duty graphics card to run Lightroom, but you will benefit from the latest drivers that are available from the graphics card manufacturers. If you haven't checked recently, that's your first port of call for a free and easy performance fix.
Next, if you have an nVidia graphics card, a quick Google will bring up numerous pages of tweaks which can make a massive difference to Lightroom's speed, particularly for sticky sliders, slow preview refreshes, and Adjustment Brush problems. Most notably, disable the nView software which is installed along with nVidia drivers, as there are known conflicts.
Hard drives are another obvious place to look. For a start, you'll want plenty of space on your hard drives, particularly the boot drive, as your computer will get slower as you start to run out of space. If you're on Windows, defragment your hard drives regularly too.
Hard drive connections can also slow down Lightroom, due to the amount of data transfer when working with large files. Internal drives will usually be quickest. If you have to work from external drives, eSata and Firewire800 will be much quicker than Firewire400 or USB. Ideally your catalog (and the previews alongside) will be on a different drive to the image files themselves.
If you're looking for new hardware, you may be wondering if Lightroom can make use of multiple cores - and yes it certainly does. I've seen it use up to 650% of my 8-core machine when running processor intensive tasks such as multiple exports or rendering previews.
Lightroom also loves plenty of RAM, but bear in mind that you'll need a 64-bit operating system to really take advantage of large amounts of RAM. If you have more than 4gb of RAM, you're most likely to see improvement in the responsiveness of Develop module by using the 64-bit version.
And finally, a little logic. Virus protection constantly scanning the same files that Lightroom's trying to use will slow you down. Consider excluding the catalog (*.lrcat), the previews file (*.lrdata next to the catalog), and the ACR Cache (check the Lightroom Preferences dialog for the location) from the live scan, and perhaps the images themselves.
The less junk you have running in the background, the better, particularly on older slower machines. That includes those fancy little system tray programs that load on startup.
That's all for now - if you have any favorite speed tips, feel free to drop them in the comments below!
by Victoria Bampton, originally posted on DWF
[Warning - this is quite long. I had originally intended to split it over a number of blog posts, but it'll be easier to reference as one post. It's on my blog, but I thought I'd post it here as it may come in handy.]
Who has never said "hurry up Lightroom"? Speed is one of the most popular feature requests from Lightroom users everywhere, and no doubt the engineers will continue working on Lightroom's performance over time, but for now, there are plenty of things you can do yourself. Some are obvious, some not so…
Speed Tips in Library module
There's a big difference between rendering previews that have never been built or that need updating, and loading those ready-built previews from disc. How can you tell the difference? The overlay in Loupe view will tell you exactly what it's doing - and therefore what you can do to help.
"Rendering Preview…" means it's rendering a preview for the first time - and you're having to wait for it! You could set Lightroom rendering the previews when it imports, by selecting your chosen preview size in the import dialog - it'll slow you down initially but once it finishes rendering, it'll be much quicker. For files that are already in your catalog, select them all in Grid view and go to Library menu > Previews > Render Standard Previews or Render 1:1 Previews, and go off and leave it until it's finished. It'll skip any that already have current previews, and you'll find browsing much quicker when it's finished.
So what size previews should you render? If you want to quickly zoom into 1:1 view in the Library module (not Develop), then it's a no-brainer - render 1:1 previews rather than Standard-Sized previews, either in the Import dialog or using the menu command noted above. On the other hand, if you rarely zoom in Library module, you're better off using Standard-Sized previews, as they'll take up less disc space and be quicker to read from the cache.
If you see the "Rendering: Higher Quality…" overlay, it means the existing preview is too small or too low quality. If you're seeing that overlay in Fit or Fill view, you'll want to reconsider your Standard preview size. You'll find those settings in the Catalog Settings dialog under the Edit menu (Windows) / Lightroom menu (Mac). Generally speaking the Medium quality setting is fine, but you may decide to increase the Standard preview size from 1440 to a larger size if you have a high resolution screen and regularly see the "Rendering: Higher Quality…" overlay.
"Rendering: File Changed…" means, well, that's the file's changed since the preview was created. That could mean that you've made changes in the Develop module, using the Quick Develop panel, or by applying a preset. Using the Render Standard Preview menu command to update those previews while you do something else will speed up your browsing.
"Loading from Previews…" is the overlay you're aiming for - that means your existing preview is being loaded from the preview cache, which is the quickest option.
Speed Tips in Develop module (or making Quick Develop changes in Library)
First, you need to understand the difference between Library module and Develop module. Library shows you lower quality previews from the previews cache. Develop, on the other hand, assumes you need an accurate view, so it first shows you the preview from the preview cache, then does a quick read of the raw file, frees up the sliders for you to start working, and then finishes loading properly, before it turns off the "Loading…" overlay. You don't have to wait for the overlay to disappear before starting work on the image - and if you find it distracting, you can turn it off in the View menu > View Options > Loupe panel > 'Show message when loading or rendering photos'.
That's all well and good, but that's still a lot of raw data to load and process each time you switch images. Have you ever noticed, though, that when you adjust a file in Develop, move to another image, and then come back to that first image again, it loads much quicker than it did the first time? That's where the Camera Raw cache, also known as the ACR cache, comes in. When Lightroom reads the data the first time, it adds it into the shared Camera Raw cache. When you load that image into Develop module, where possible, it will load that cached data, which is much quicker than reading and processing the original raw file data.
By default, that Camera Raw cache is only 1gb in size, and when new data gets added, the oldest data is removed. With only 1gb of space, that happens quite quickly, so you're not seeing the benefit. If you go to Lightroom's Preferences dialog, and look in the File Handling tab, you can change the cache size to suit - up to a maximum of 50gb. Bigger is better! You can also change the location if you wish to - but make sure it's on a fast hard drive.
Once that data is cached, it's much faster moving between images in the Develop modules - almost instantaneous on high end machines. Of course, that is only helpful when Lightroom has recently read the raw file, and added it to the cache - and there isn't currently a menu command to pre-load the Camera Raw cache. All is not lost!
There's a trick to pre-loading the Camera Raw cache - in addition to actually viewing the image in Develop module, there's another obvious time when Lightroom has to read (and therefore caches) the raw data - namely, when rendering previews. If you haven't already rendered previews for your files, simply using the Library menu > Render Standard-Sized Previews command will do the trick. If, however, you already have current previews, you can force them to re-render by making a minor or reversible change to the images (i.e. by using a Quick Develop button) and then using the Render Standard-Sized Previews menu command. Leave it to finish, and by the time you come back, even the Develop module should be moving through the images at a much more comfortable speed.
Dispelling the Catalog Myths
It's true that large catalogs can be a little slower than small catalogs - but we are talking BIG catalogs. It's not generally a good reason (any more) to split your library into 300 different catalogs - that just defeats the object of having a DAM system like Lightroom.
If you find Lightroom is feeling a little sluggish, find the Catalog Settings dialog under the Edit menu (Windows) / Lightroom menu (Mac), and press the "Relaunch and Optimize" button to perform database optimization. It's worth doing regularly, and any time you make significant database changes like importing or removing large numbers of files.
Finally, Hardware Tips & OS Tweaks
There is no question, Lightroom loves good hardware, but it can still run nicely on older systems too. Do make sure you're running the latest Lightroom release (currently 2.3) as performance improvements have been made to each release.
The system requirements are listed as Intel Pentium 4 or equivalent (i.e. a processor with the SSE2 instruction set or later), with 1gb of RAM and 1gb of hard drive space. Now let's be clear - those are minimum system requirements. It'll run - well, it'll walk! But if you start trying to feed 5d Mk2 files into Lightroom with a computer that was in the Ark, don't expect it to be fast, and don't complain about the speed. If you're going to spend money on the latest and greatest cameras, bear in mind that your computer hardware may also require a helping hand with those new super-size files. Yes, even those sRAW files. ;-)
If you're working with existing hardware, check your graphics card. You don't need a heavy-duty graphics card to run Lightroom, but you will benefit from the latest drivers that are available from the graphics card manufacturers. If you haven't checked recently, that's your first port of call for a free and easy performance fix.
Next, if you have an nVidia graphics card, a quick Google will bring up numerous pages of tweaks which can make a massive difference to Lightroom's speed, particularly for sticky sliders, slow preview refreshes, and Adjustment Brush problems. Most notably, disable the nView software which is installed along with nVidia drivers, as there are known conflicts.
Hard drives are another obvious place to look. For a start, you'll want plenty of space on your hard drives, particularly the boot drive, as your computer will get slower as you start to run out of space. If you're on Windows, defragment your hard drives regularly too.
Hard drive connections can also slow down Lightroom, due to the amount of data transfer when working with large files. Internal drives will usually be quickest. If you have to work from external drives, eSata and Firewire800 will be much quicker than Firewire400 or USB. Ideally your catalog (and the previews alongside) will be on a different drive to the image files themselves.
If you're looking for new hardware, you may be wondering if Lightroom can make use of multiple cores - and yes it certainly does. I've seen it use up to 650% of my 8-core machine when running processor intensive tasks such as multiple exports or rendering previews.
Lightroom also loves plenty of RAM, but bear in mind that you'll need a 64-bit operating system to really take advantage of large amounts of RAM. If you have more than 4gb of RAM, you're most likely to see improvement in the responsiveness of Develop module by using the 64-bit version.
And finally, a little logic. Virus protection constantly scanning the same files that Lightroom's trying to use will slow you down. Consider excluding the catalog (*.lrcat), the previews file (*.lrdata next to the catalog), and the ACR Cache (check the Lightroom Preferences dialog for the location) from the live scan, and perhaps the images themselves.
The less junk you have running in the background, the better, particularly on older slower machines. That includes those fancy little system tray programs that load on startup.
That's all for now - if you have any favorite speed tips, feel free to drop them in the comments below!
Re[Brandon]:
Помогите, пожалуйста, решить следующую проблему. На диске С: в Программных файлах записана программа Лайтрум 2.4. Соответственно, и обработка происходит на этом же диске. Но импорт файлов RAW происходит с переносного жесткого диска и экспорт уже обработанных файлов также на переносной жесткий диск. Но после 1-1,5 часов работы в программе появляется сообщение о недостатке свободного места именно на диске С:, и я не могу загрузить и обрабатывать файлы в программе. Уже пыталась и чистить диск, все равно никаких результатов! 15 гигов занялось непонятно чем. Папка Мои рисунки\lightroom\bacup - пуста.
Re[Tanya_S]:
от:Tanya_S
На диске С: в Программных файлах записана программа Лайтрум 2.4. Соответственно, и обработка происходит на этом же диске. Но импорт файлов RAW происходит с переносного жесткого диска и экспорт уже обработанных файлов также на переносной жесткий диск. Но после 1-1,5 часов работы в программе появляется сообщение о недостатке свободного места именно на диске СПодробнее
вы сами ответили на свой вопрос. Либо освободите место на диске C
либо НИКОГДА не держите базу и RAW файлы на диске С!
все на отдельном диске, они сейчас дешевые! и про внешний тоже забудьте, USB 2 не быстрый интерфейс. Попробуйте eSATA или USB 3.0 для внешнего диска
и еще зачем импортировать и экспортировать на внешний? держите все на нормальном отдельном диске
Re[igoralekseev.com]:
Вот поэтому у меня все файлы (и RAW тоже) на отдельном диске хранятся. Я уже и превьюшки абсолютно все удалила с диска С. Вот есть какой-то файл в папке Мои документы\Лайтрум - Catalog.Lightroom.lrcat (или что-то в этом роде), не в нем ли хранится вся информация об обработке моих файлов? Я пыталась его открыть - он мне выдавать начинает предустановки Виндоус. Почему так много места крадется на диске С, если я на него вообще ни один файл не записываю? Я только загружаю RAWы для обработки, а затем все превью удаляю полностью .
