This confounds photolibraryd so that it stops thrashing the computer.
Giving myself R&W access to all the contents stopped the disk-writing churn and the errors that were showing up in Console.app from photolibraryd, however it still continued to dump tons of non-error messages into Console and was reading continuously from the HD at 15MB/s for hours despite the fact that I don't have enough photos to occupy it for more than a couple minutes at that speed.Īt this point, the advice here from mbackschat on worked instead, which is to rename the folder ~/Pictures/Photos Library.photoslibrary/database to something else (for example, to database.xxx). I had previously given myself Read & Write privileges for the overall Photos Library bundle, but this was not enough. I had to open the bundle (go to ~/Pictures/Photos Library.photoslibrary and right-click it, then choose "Show Package Contents"), Get Info on each subfolder (database/, external/, originals/, etc.), and under the Sharing & Permissions section add my new user account, set its privileges to "Read & Write", and then click the ellipsis-in-a-circle button at the bottom and choose "Apply to enclosed items…". This problem was partially due to the fact that my new account did not own the files inside the Photos Library bundle. This started when I moved the Photos library from one user account to another on the computer. In my case, it was photolibraryd and not photoanalysisd that was hogging CPU and also causing massive HD churn, but I'd like to provide an answer here that worked for me in stopping photolibraryd, because (1) I think these tips will work for stopping photoanalysisd too, (2) this page is one of the top Google results for people searching for info about photolibraryd, and (3) none of the advice on this page (as of ) worked for me in stopping photolibraryd.įirst, I was initially experiencing massive disk churn, particularly disk- writing not reading. Note, however, that minimising the Photos app will act to restart the photoanalysisd daemon, so just leave it running in the background while you want to keep the daemon paused.
#Mac computer image analyse free#
Should you need to pause the process in order to free up some of your CPU, I would recommend just opening the Photos app for a while and then quitting it when you’re not using the computer. The fact that Photos isn’t running actually fits with your scenario, as launching the Photos app will pause the photoanalysisd daemon.Īlthough it takes a long time, once it’s finished your Photos app will be able to perform a lot of advanced functions due to all the metadata etc it’s processed, so I would let it finish what it’s doing. If you suspect this has been the cause of your sluggishness for a couple of days, then it’s most likely you’ve got a very large photo library and that it’s being processed for the first time on your new iMac. Your iMac is currently processing the photos in your Photos library, presumably because you’ve just imported/converted an existing Photos library from an earlier version of macOS.