Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
Apple Computing Products:
macOS - Apps and Programs
Apple Photos processing, memory, CPU problems
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="MacInWin" data-source="post: 1662055"><p>25GB is a large library of pictures. And it can take quite a while for the initial indexing to occur. Combine that factor with having only 4GB of RAM and you are undoubtedly having HUGE swapping (you can check that by looking at the memory tab in Activity Monitor. At the bottom is your Memory status, including Swap Used. If you are using swap, you are writing memory to the HD when memory gets full, then reading it in when it's needed again. That is SLOOOOOOOW). So, when the application pulls in another picture, it has to write out some of what's in memory to get space to put that image, process the image, maybe swap something else out to make room for the part of the program to process that image, then repeat that process for the next, etc, etc, etc (yes, that's simplistic because a lot more is going on, but you get the idea). Eventually you got to 40GB of RAM, which means every time it has to swap something out it has to write out almost 40GB to the HD! Then if it finds it needs something in that 40GB, it's got to go find it and read it back in, probably writing something else out to make room. So, get more memory for your machine, at least 8GB, but with that kind of photo production going on and using it for work, you probably ought to get the MAX you can jam in that machine. The goal is to have zero Swap Used.</p><p></p><p>As for the CPU utilization, greater than 100% is logical in that 100% is one core and you have a multi-core CPU. So you can see greater than 100% if more than one core is in use.</p></blockquote><p></p>
[QUOTE="MacInWin, post: 1662055"] 25GB is a large library of pictures. And it can take quite a while for the initial indexing to occur. Combine that factor with having only 4GB of RAM and you are undoubtedly having HUGE swapping (you can check that by looking at the memory tab in Activity Monitor. At the bottom is your Memory status, including Swap Used. If you are using swap, you are writing memory to the HD when memory gets full, then reading it in when it's needed again. That is SLOOOOOOOW). So, when the application pulls in another picture, it has to write out some of what's in memory to get space to put that image, process the image, maybe swap something else out to make room for the part of the program to process that image, then repeat that process for the next, etc, etc, etc (yes, that's simplistic because a lot more is going on, but you get the idea). Eventually you got to 40GB of RAM, which means every time it has to swap something out it has to write out almost 40GB to the HD! Then if it finds it needs something in that 40GB, it's got to go find it and read it back in, probably writing something else out to make room. So, get more memory for your machine, at least 8GB, but with that kind of photo production going on and using it for work, you probably ought to get the MAX you can jam in that machine. The goal is to have zero Swap Used. As for the CPU utilization, greater than 100% is logical in that 100% is one core and you have a multi-core CPU. So you can see greater than 100% if more than one core is in use. [/QUOTE]
Verification
Name this item. 🍎
Post reply
Forums
Apple Computing Products:
macOS - Apps and Programs
Apple Photos processing, memory, CPU problems
Top
