macOS Contacts ( contactsd ) daemon burning hours of CPU and reading gigabytes of data from disk

Hi. I have macOS connected to Google Contacts, with about 8,000 contacts. On my Mac Studio, the contactsd daemon burns enormous amounts (hours upon hours) of CPU time. contactsd also reads huge amounts of data from disk. To give you some perspective, my Mac's uptime is currently 18 hours, but contactsd has already used 4 hours and 30 minutes of CPU time and it has also read 4.2GB of data from disk. When I do a full contacts backup, all 8,000 contacts total up to less than 5MB, so this means the entire contacts database has been read about 1,000 times since yesterday. Something is seriously wrong with either the Contacts app or the way it interacts with Google Contacts. This has been going on for a few years now, so it is not specific to any version of macOS. I just updated to Ventura 13.3 yesterday morning and it is still not fixed.

Posted on Mar 28, 2023 5:30 AM

Reply
Question marked as Top-ranking reply

Posted on Apr 4, 2023 8:55 AM

To even further reduce the residual CPU consumption of the contactsd daemon, I had to disable Siri Suggestions. I noticed that suggestd and contactsd were still burning CPU together. When I disabled Siri Suggestions and rebooted, contactsd CPU usage fell to almost nothing. Settings --> Siri Suggestions, toggle to off position. And on a related note, if you happen to see photoanalysisd burning CPU at the same time as contactsd, you might try going into Apple Photos (View --> Photos --> People) and deleting any people that Apple Photos may have tagged. I believe that photoanalysisd and contactsd can burn a lot of CPU time trying to match faces of people in Apple Photos with people in Apple Contacts. If searching by people's names in Apple Photos is not important to you, it might help to delete any existing photos that Apple Photos is searching through to match with faces in Apple Contacts.

3 replies
Question marked as Top-ranking reply

Apr 4, 2023 8:55 AM in response to mrabne

To even further reduce the residual CPU consumption of the contactsd daemon, I had to disable Siri Suggestions. I noticed that suggestd and contactsd were still burning CPU together. When I disabled Siri Suggestions and rebooted, contactsd CPU usage fell to almost nothing. Settings --> Siri Suggestions, toggle to off position. And on a related note, if you happen to see photoanalysisd burning CPU at the same time as contactsd, you might try going into Apple Photos (View --> Photos --> People) and deleting any people that Apple Photos may have tagged. I believe that photoanalysisd and contactsd can burn a lot of CPU time trying to match faces of people in Apple Photos with people in Apple Contacts. If searching by people's names in Apple Photos is not important to you, it might help to delete any existing photos that Apple Photos is searching through to match with faces in Apple Contacts.

Apr 3, 2023 10:38 AM in response to Brittany1416

SOLVED. (At least for me) Over the weekend, I moved all 8,000 of my contacts from Google Contacts back to iCloud Contacts. macOS CPU and disk usage has dramatically reduced to the point of not being an issue any longer. Also, the issue of starting to create a new contact in Apple Contacts and having the window close prematurely is now gone. I really hope Apple can work with Google Contacts to figure out how to make macOS Contacts and Google Contacts work together.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

macOS Contacts ( contactsd ) daemon burning hours of CPU and reading gigabytes of data from disk

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.