# Expected Framerate 13000 LEDs **URL:** \ **Category:** Uncategorized\ **Created:** [July 11, 2021, 9:52am UTC](https://forum.electromage.com/t/expected-framerate-13000-leds/1382 "2021-07-11T09:52:39Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![wizard](https://forum.electromage.com/user_avatar/forum.electromage.com/wizard/32/4_2.png) [@wizard](https://forum.electromage.com/u/wizard)\ **Post date:** [July 14, 2021, 12:53am UTC](https://forum.electromage.com/t/expected-framerate-13000-leds/1382/10 "2021-07-14T00:53:07Z")
> [@Scruffynerf](#): > > as I was reviewing older posts looking for code… > > In your case, having 13000 pixels in each map/PB might be too much… 13K pixels in a 3D map will definitely push a few limits. The map would be 78k of coordinate data which has to sit in memory. There might be enough RAM, but I would’t recommend it. What I’d recommend for something this large and going with the extra pixels method would be to have a few extra marker pixels (in the map only), just enough to keep the map coordinates scaled to the larger world, so it doesn’t normalize to the single subsection’s coordinate space. I do not recommend setting the pixel count to 13k on each subsection. It is unnecessary to keep multiple PBs in sync for `time()` based patterns. @LEDCreate, Some animation methods in some patterns do not lend themselves to parallelization across a Firestorm of Pixelblaze, which relies on synchronized animation time bases. KITT is an example of a pattern that doesn’t use `time()`, and instead uses the relative passage of time with `delta` and incremental calculations in `beforeRender()`. In cases like that, Firestorm/timesync can’t keep them synchronized. However, we’ve recently had some fun [noodling how to make a `time()` based KITT](https://forum.electromage.com/t/kitt-without-arrays/1219) that would parallelize via a Firestorm setup with timesync. --- _[View the full topic](https://forum.electromage.com/t/expected-framerate-13000-leds/1382)._