unity-collection-pool

Use Unity's built-in pooling primitives—ListPool, DictionaryPool, and HashSetPool—to reuse collection instances instead of allocating new ones. Obtain a collection via Get(), use it, then Release() it back to the pool to avoid GC allocations in high-frequency scenarios like per-frame processing.

ListPool provides GC-free temporary list management through Get/Release patterns. Retrieve a list, populate it for your operation, and return it to the pool immediately. The pool clears the list automatically on retrieval, enabling safe reuse across frames.

Yes. DictionaryPool and HashSetPool follow identical Get/Release patterns as ListPool. All three integrate with Unity's using statement for automatic release, making them interchangeable pooling solutions for different collection types.

Apply pooling to high-frequency, short-lived collection scenarios: temporary lookups, duplicate checks, per-frame batching, and processing temporary lists. Pooling eliminates GC pressure when operations repeat every frame or in tight loops across gameplay sessions.

ObjectPool follows similar lifecycle principles but is generic and applies to custom object types, not built-in collections. It shares the Get/Release pattern and pool lifecycle discipline but requires manual Clear() logic and type-safe instantiation for non-collection objects.