# CacheAsBitmap or draw() - Quick question

**URL:** <https://forum.kirupa.com/t/cacheasbitmap-or-draw-quick-question/294166>\
**Category:** flash\
**Created:** [August 10, 2009, 10:15am UTC](https://forum.kirupa.com/t/cacheasbitmap-or-draw-quick-question/294166 "2009-08-10T10:15:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![four4swords](https://avatars.discourse-cdn.com/v4/letter/f/87869e/32.png) [@four4swords](https://forum.kirupa.com/u/four4swords)\
**Post date:** [August 10, 2009, 10:15am UTC](https://forum.kirupa.com/t/cacheasbitmap-or-draw-quick-question/294166/1 "2009-08-10T10:15:42Z")

</div>

Hi,

I’m currently building a huge map made from tiles for a game I’m making and I was wondering, which method is better. Please note, these tiles will be moved around the stage, however , no modifications like changing scale or rotation will be used.

[INDENT]1. To either attachMovie() all my tiles into one movieclip to hold them all. Then to set cacheAsBitMap to true.  
[/INDENT]  
Or

[INDENT]2. To attach all my tiles into one movieclip, then by using the draw() function, to draw all my tiles in the movieclip onto a bitMap and attachBitmap that to the stage, and then remove all my movieclips from the stage as they are no longer needed.  
[/INDENT]  
Which method do you think is better? On my computer, I can see no noticable change in framerate, and they both seem pretty fast. The draw() method does seem to give a slightly smoother scrolling animation, but on looking back, they both seem to stagger at times, although overall a smooth scrolling animation.

Which method is better in terms of performance and memory?

Also, bitMapData has a limit of 2880pixels in height and width, but does this apply to movieclips which have cacheAsBitmap turned on?

Thanks