Welcome, Kayezad, to Apple Support Communities!
All three of those («CalanderAgent and sharingD and sugdestD») processes are background processes.
(Incidentally, the background processes that end in a “d” [almost invariably, a lowercase “d”] are called “daemons”, in UNIX parlance. A daemon is “a helpful little spirit”.)
The CalendarAgent is the backend of the Calendar App. This could simply be “housekeeping”, in trying to index your calendars to be ready for your needs, such as reminders, searches, etc.
However, if it has been doing this for days, or longer, there’s probably something wrong, probably with one or more of your calendars.
Remember that many of your calendars are associated with your email accounts.
(Some people, usually on iPhones, get conned into installing malicious “rouge” calendars, that, mostly, “flood” the user with scary messages about “viruses” and being “hacked”.)
People have, at times, had trouble with the CalendarAgent taking up 100% CPU on many previous versions of macOS. I did a quick Google search, and such were the major “hits”.
Making sure your various calendars are good and “clean” is the universal fix, here.
sharingd is a sharing daemon that enables AirDrop, Handoff, Instant Hotspot, Shared Computers, and Remote Disc in the Finder.
It has, likewise, been implicated in cases of high CPU usage in previous macOSs.
As you can see from the list of functions that sharingd can be involved in, there could be multiple causes for high CPU usage.
Again, if such CPU usage doesn’t “settle down” in a day or two, you may want to take a look at what file sharing processes you have on your system, particularly third-party.
The suggestd daemon receives content from Spotlight, Mail, Messages and various other apps in order to power various features. Those features include Found in Apps, Proactive QuickType, and Keyboard/Siri/News Personalization.
This one, likewise, has been implicated in high CPU use in previous macOSs.
This is the primary indexer for your future searches, of various kinds. Depending upon how many files you have, this can take days to “catch up”. Once it is caught up, it will only run as you change or add files.
So. The good news is:
- These are standard processes on macOS.
- These should “settle down”, under normal situations.
These have all been involved in high CPU and other computer resource usage even in much older versions of macOS. So, this is nothing unique to Big Sur.
The bad news is:
- Since these processes can interface with third-party systems, problematic third-party systems can cause them trouble.
- Since these processes are involved with many files and/or systems, it is not trivial to find the issue as that may be causing any misbehaviors.
Fortunately, since these background processes have been involved with past instances of high CPU and other computer resource use in previous macOSs, there is a good body of information that can be found on the Internet that may be of help.
I do, however, wish I had more definitive news for you. 😔