# Spawn and Destroy VS Spawn and Re-use

**URL:** <https://forums.unrealengine.com/t/spawn-and-destroy-vs-spawn-and-re-use/488603>\
**Category:** Debugging, Optimization, & Profiling\
**Tags:** Optimization, Destroy-Actor, unreal-engine, spawning-actors, question\
**Created:** [September 10, 2021, 2:04am UTC](https://forums.unrealengine.com/t/spawn-and-destroy-vs-spawn-and-re-use/488603 "2021-09-10T02:04:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thee\_MuffinMan](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Thee\_MuffinMan](https://forums.unrealengine.com/u/Thee_MuffinMan)\
**Post date:** [September 10, 2021, 2:04am UTC](https://forums.unrealengine.com/t/spawn-and-destroy-vs-spawn-and-re-use/488603/1 "2021-09-10T02:04:13Z")

</div>

Is it better To Spawn an actor then destroy it over and over  
OR  
Spawn an actor once and re-use it with extra code to hide and show it.

This question is entirely for optimization reasons.

For my purpose these actors are spawned and destroyed infrequently (1-6 Seconds), spawn and destroy is a lot easier and cleaner to work with however it feels wrong.  
(More Specifically It’s for “Add Actor Comp Child”)

---

<div class="post-metadata">

**Author:** ![Everynone](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/everynone/32/1135017_2.png) [@Everynone](https://forums.unrealengine.com/u/Everynone)\
**Post date:** [September 10, 2021, 7:41am UTC](https://forums.unrealengine.com/t/spawn-and-destroy-vs-spawn-and-re-use/488603/2 "2021-09-10T07:41:12Z")

</div>

> Is it better To Spawn an actor then  
> destroy it over and over OR Spawn an  
> actor once and re-use it with extra  
> code to hide and show it.

It’s generally better to reuse but…

* * *

If it’s only several actors and it’s only every other second or so _and_ you feel it makes it cleaner, easier to organise and maintain, that’s the way I’d lean - Destroy/Spawn.

* * *

[Object Pooling is a thing for a reason.](https://en.wikipedia.org/wiki/Object_pool_pattern) It’d make sense to employ it if performance was paramount; it’s worth it providing you need a large enough pool to justify the upfront cost of setting it up.