Can you provide a same project we can test ourselves? There could be any number of things going on here, so we need to run the code ourselves to see. But generally I've found Swift concurrency to be pretty bad at these sorts of unbounded parallelism problems, if for no other reason but that TaskGroup isn't actually a parallel construct, it simply guarantees concurrency. A comparison to DispatchQueue.concurrentPerform or other queue usage might be informative.
1 Like