# P3D performance with 62500 boxes

**URL:** <https://discourse.processing.org/t/p3d-performance-with-62500-boxes/3821>\
**Category:** Coding Questions\
**Created:** [September 25, 2018, 7:57am UTC](https://discourse.processing.org/t/p3d-performance-with-62500-boxes/3821 "2018-09-25T07:57:37Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![coco](https://avatars.discourse-cdn.com/v4/letter/c/8797f3/32.png) [@coco](https://discourse.processing.org/u/coco)\
**Post date:** [March 2, 2019, 6:38pm UTC](https://discourse.processing.org/t/p3d-performance-with-62500-boxes/3821/24 "2019-03-02T18:38:33Z")

</div>

I tried the 3.5.3 version but same bottleneck.  
it is definitely the shapes[i].translate line that slows everything way down.

for (int i = 0; i \< shapes.length; i++) {  
shapes[i].resetMatrix();  
shapes[i].translate(m.x, m.y, m.z);  
}  
it is so frustrating because i don’t know what to do to move forward. I absolutely need to port my very long 151 + GLGraphics program to P3 very soon. any suggestions, anyone ? help !

---

_[View the full topic](https://discourse.processing.org/t/p3d-performance-with-62500-boxes/3821)._