# \[Pitch\] Core team publishes results of performance study: Cooperative Scheduler just introduced, plus compile for non-atomic ARC

**URL:** <https://forums.swift.org/t/pitch-core-team-publishes-results-of-performance-study-cooperative-scheduler-just-introduced-plus-compile-for-non-atomic-arc/65632>\
**Category:** Pitches\
**Created:** [June 16, 2023, 9:23pm UTC](https://forums.swift.org/t/pitch-core-team-publishes-results-of-performance-study-cooperative-scheduler-just-introduced-plus-compile-for-non-atomic-arc/65632 "2023-06-16T21:23:01Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![johnburkey](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/johnburkey/32/20566_2.png) [@johnburkey](https://forums.swift.org/u/johnburkey)\
**Post date:** [June 22, 2023, 2:31am UTC](https://forums.swift.org/t/pitch-core-team-publishes-results-of-performance-study-cooperative-scheduler-just-introduced-plus-compile-for-non-atomic-arc/65632/27 "2023-06-22T02:31:55Z")

</div>

Oh and for us, the rest of the story is for classes where we do this, we have a resizable pool of instances that are allocated once and cleaned for reuse.

It makes mass allocations essentially free and ARC almost gone (still those high frequency calls to the retain/release hooks).

Going further into the future - as we move away from unified memory as our core counts grow - you could imagine single core allocators that use this same motif and are even cheaper . (Single core single thread allows don’t use locks)

This whole thing can be done inside the language ! So people don’t see all this complexity and get even more of a win !

So hey, thanks Tera for leading the charge!

Love swift 🇺🇦

---

_[View the full topic](https://forums.swift.org/t/pitch-core-team-publishes-results-of-performance-study-cooperative-scheduler-just-introduced-plus-compile-for-non-atomic-arc/65632)._