You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really like this plugin and am in the process of publishing around 4.500, primarily, photos and some videos through it.
Bandwith (2,5GBps) CPU and memory on both the system running Lightroom and the Immich server shouldn’t be a limiting factor, but I am now already 12 hours publishing and am only halfway through. Exporting such a bunch of photos should normally take around 2 hours. Also importing 200gigabyte of Google takeout photos (through Immic-go) goes much faster.
Could it be the case that the plugin is slowing things a bit down? Any tips on how I can pinpoint the bottleneck?
The text was updated successfully, but these errors were encountered:
Are the Immich server and the computer running Lightroom running in the same network? Did you use the internal or external address of your Immich server in the Lightroom configuration? At my place I exported about 20.000 photos from Lightroom to Immich, but it didn't take that long. But I used the internal address for that, so that the process isn't slowed down by a LAN-WAN-LAN route.
I have seen similar behaviour when publishing. But its the same for the Lightroom-to-Synology Plugin I use. Therefore I guess the problem is inside Lightroom.
I really like this plugin and am in the process of publishing around 4.500, primarily, photos and some videos through it.
Bandwith (2,5GBps) CPU and memory on both the system running Lightroom and the Immich server shouldn’t be a limiting factor, but I am now already 12 hours publishing and am only halfway through. Exporting such a bunch of photos should normally take around 2 hours. Also importing 200gigabyte of Google takeout photos (through Immic-go) goes much faster.
Could it be the case that the plugin is slowing things a bit down? Any tips on how I can pinpoint the bottleneck?
The text was updated successfully, but these errors were encountered: