# Is it bad to have lots of onEnterFrames running concurrently?

**URL:** <https://forum.kirupa.com/t/is-it-bad-to-have-lots-of-onenterframes-running-concurrently/212163>\
**Category:** Uncategorized\
**Created:** [January 8, 2007, 11:26pm UTC](https://forum.kirupa.com/t/is-it-bad-to-have-lots-of-onenterframes-running-concurrently/212163 "2007-01-08T23:26:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dalewb](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/dalewb/32/3029_2.png) [@dalewb](https://forum.kirupa.com/u/dalewb)\
**Post date:** [January 8, 2007, 11:26pm UTC](https://forum.kirupa.com/t/is-it-bad-to-have-lots-of-onenterframes-running-concurrently/212163/1 "2007-01-08T23:26:59Z")

</div>

Only recently have I understood that onEnterFrame creates a continuously-running program that runs at the same framerate as the movie (until you call a "delete enterFrame). So, if I have a bunch of these running at the same time will I see a big speed drop? I’m a bit leery about using onEnterFrame because of this. Are there any alternatives to this method? I haven’t been able to find any (short of putting onClipEvent handlers on movie clips).
