# Scheduling CPU work efficiently Use concurrent programming and adjust the prioritization of background activities to improve the performance of your app. ## Overview Reduce the total computation your app does by adopting these strategies: - Choose an efficient algorithm. - Cache frequently used results in memory, instead of recalculating them each time your app needs to use the results. - Reuse structures and objects to avoid the overhead of releasing and reallocating instances. - Prefer an event-driven design, in which your app’s code receives notifications when it needs to perform work, instead of polling for available tasks. - Use high-level system frameworks to achieve your app’s goals, because these are optimized to reduce power overhead. For example, use to work with machine learning models, and to perform video processing. Additionally, reduce the amount of energy your app uses to perform calculations on the CPU by avoiding CPU bottlenecks, which reduce the CPU’s efficiency. For more information, see [Addressing CPU bottlenecks](/documentation/Xcode/addressing-cpu-bottlenecks). ### Adopt concurrent programming Use concurrent programming techniques, such as [Swift Concurrency](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/concurrency/) or , to efficiently schedule work on multiple CPU cores. Adopting concurrent programming also helps to avoid hangs and hitches in your app by moving processing work to background threads. For more information, see [Improving app responsiveness](/documentation/Xcode/improving-app-responsiveness). Identify a granularity for concurrent operations that balances creating multiple operations that the CPU can schedule on multiple cores, with performing enough work in each operation to avoid creating too much overhead in managing the operations. Ideally, each independent operation requires between 10-100 ms to complete. Set the (quality-of-service, or QoS) level for concurrent operations, to ensure that the system schedules UI-related tasks responsively and uses efficient strategies to complete background operations. In general, use the lowest QoS value that makes sense for your task, because the system uses more energy-efficient scheduling for tasks with lower QoS. For more information on setting QoS for operations, see . The Thread Performance Checker in Xcode reports runtime issues if you create dependencies from high-QoS operations on low-QoS operations. For more information on using the Thread Performance Checker, see [Diagnosing performance issues early](/documentation/Xcode/diagnosing-performance-issues-early). ### Schedule work in the background Use to perform work in the background. The system optimizes the schedule for background tasks — for example by batching tasks together or by running the tasks when the device is charging. For more information, see . ### Prioritize Live Activities appropriately Whenever you send a push notification that contains an update to your app’s Live Activity that doesn’t require immediate attention from someone, set the value for the `apns-priority` HTTP header to `5`, which indicates to the Apple Push Notification service (APNs) server that it can deliver the push notification in an energy-efficient way. Notifications with `apns-priority` set to `5` don’t count toward your app’s budget for Live Activity updates, so setting the value to `5` helps reduce the likelihood that your app exceeds its budget. If the app does exceed its budget, the system reduces the rate at which it delivers your notifications. For more information, see . --- Copyright © 2026 Apple Inc. All rights reserved. | [Terms of Use](https://www.apple.com/legal/internet-services/terms/site.html) | [Privacy Policy](https://www.apple.com/privacy/privacy-policy)