Trying to use the Auto Add Photos functionality on a large photo library on a Mackbook M4 with 24 gb of memory. After running through about 2K pictures (none of which are actually added, nor should they be because they're not applicable), it freezes having used all available RAM. I have more than 20K photos so don't want to have to export 2K at a time to another folder for this to work. It would be amazong functionality and solves a real problem for me if it worked.
Does anyone have a similar experience and/or have an idea how to address?
Thanks in advance for any help.
Auto Add Photos Using All Available Memory
-
nick
- Site Admin
- Posts: 4378
- Joined: Sat Apr 12, 2008 8:33 am
- Dive Computer: Shearwater Teric
- Contact:
Re: Auto Add Photos Using All Available Memory
Have not run in to this before. It does however create a UI with what matched and what didn’t - I suspect it’s caching way too much.
24GB is a lot of data. Are these raw images or something? How many photos are there?
The workaround, obviously, is to do less at once - or export smaller versions. Which is what typically do, keep my full res/raw images and export far smaller ones to add. 24GB is a huge amount of smaller photos..
24GB is a lot of data. Are these raw images or something? How many photos are there?
The workaround, obviously, is to do less at once - or export smaller versions. Which is what typically do, keep my full res/raw images and export far smaller ones to add. 24GB is a huge amount of smaller photos..
Re: Auto Add Photos Using All Available Memory
Thanks for your reply. When I mentioned 24Gb, I was referring to the ram on my MacBook, I should have been more clear. All of the images are either jpg or HEIC. While, I’ve over 20k pictures to go through, 2K of them are definitely not 24 Gb worth.
Either way, while it would be great if it worked, it’s certainly a first world problem. I have all the pictures on my camera roll anyway so it’s not the end of the world by any stretch. At some point, when I have a bunch of free time, I’ll probably create batches to overcome it.
All that said, it seems odd to me that it would cache the pictures it has ruled out. I would think all it would have to do it just keep the file name and only cache applicable images (in which case I’d still eventually run into the issue but I could do larger batches than just 2k at a time).
Again, thank you for your response, much appreciated.
Either way, while it would be great if it worked, it’s certainly a first world problem. I have all the pictures on my camera roll anyway so it’s not the end of the world by any stretch. At some point, when I have a bunch of free time, I’ll probably create batches to overcome it.
All that said, it seems odd to me that it would cache the pictures it has ruled out. I would think all it would have to do it just keep the file name and only cache applicable images (in which case I’d still eventually run into the issue but I could do larger batches than just 2k at a time).
Again, thank you for your response, much appreciated.