DAS and CTS are largely responsible for work by E cores. DAS typically submits more than 700 activities for scheduling, including those for Time Machine backups, which have changed in Sonoma and later, with implications for LaunchAgents and LaunchDaemons settings.
DAS
Have your Time Machine backups become irregular, or stopped altogether? Are software updates infrequent, or malware scans rare? Find the answers here.
After logging in, macOS may check for system software updates, run an initial Time Machine backup, and run XProtect Remediator scans. This is how those happen.
Apps often have to use separate services to perform privileged tasks for them, or run time-consuming activities in the background. XPC is how the client communicates with those services.
In a quest to reduce the number of processes running in macOS Tahoe, consider the example of Time Machine backups, which can easily be replaced by 3rd party alternatives.
The new medium of the latter half of the 20th century, and how pioneers like Sam Golden transformed it to make it suitable as a replacement for oils.
Since the update to XProtect Remediator version 151, many have seen warnings of a plugin being cancelled. This explains how that happens, and what you can do about it.
Users should be given a third option to defer updating further, as well as doing it now or later tonight. Does the DAS scheduling and dispatch system rely on security through obscurity too?
How DAS gathers its budgets and loads lists of activities. When rescoring permits, it then dispatches the process to initiate backup. Re-scheduling has changed in Sequoia, as shown here.
Easy to code, these don’t need to use XPC although it’s used by the DAS-CTS scheduling and dispatch system. They aren’t run at constant time intervals, but when appropriate according to other loads.
The Eclectic Light Company 