Is it efficient to create many tasks?
Updated for Xcode 14.2
Previously I talked about the concept of thread explosion, which is when you create many more threads than CPU cores and the system struggles to manage them effectively. However, Swift’s tasks are implemented very differently from threads, and so are significantly less likely to cause performance problems when used in large numbers, and in fact one of the Swift team who worked on it said that unless you’re creating over 10,000 tasks it’s not worth worrying about the impact of so many tasks.
That doesn’t mean creating so many tasks is necessarily the best idea. You might think that’s hard to do, but a task group calling addTask() inside a loop might create several hundred or even several thousand depending on what you were looping over. And that’s okay. Again, even if you’re creating well over 10,000 tasks it’s not likely to cause a problem as long as you know that’s what you’re doing – if that’s the architectural choice you’re making after evaluating the alternative.
So, broadly speaking you should feel free to create as many tasks as you want, but if you ever find yourself creating tasks to transform elements inside huge arrays you might want to double-check your performance using something like Instruments.
SAVE 50% To celebrate WWDC23, all our books and bundles are half price, so you can take your Swift knowledge further without spending big! Get the Swift Power Pack to build your iOS career faster, get the Swift Platform Pack to builds apps for macOS, watchOS, and beyond, or get the Swift Plus Pack to learn advanced design patterns, testing skills, and more.
Similar solutions…
- How to create a task group and add tasks to it
- What’s the difference between async let, tasks, and task groups?
- What are tasks and task groups?
- How to run tasks using SwiftUI’s task() modifier
- How to cancel a task group
