# Hardware solutions for long renders

**URL:** https://discourse.processing.org/t/hardware-solutions-for-long-renders/32370
**Category:** p5.js
**Created:** [September 22, 2021, 9:52am UTC](https://discourse.processing.org/t/hardware-solutions-for-long-renders/32370 "2021-09-22T09:52:52Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![josephh](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/josephh/32/210_2.png) [@josephh](https://discourse.processing.org/u/josephh)
#### Post date: [September 22, 2021, 5:53pm UTC](https://discourse.processing.org/t/hardware-solutions-for-long-renders/32370/2 "2021-09-22T17:53:58Z")

</div>

Hi @goldorak,

Which renderer are you using?

You can see this previous thread about GPU and hardware accelerated rendering:

> [@Making use of the GPU to render huge amount of objects](https://discourse.processing.org/t/making-use-of-the-gpu-to-render-huge-amount-of-objects/26267):
>
> Hi, I’m new to p5.js and WebGL, so I’m not sure if I’m using the right terminology. Let’s start with the problem: We’re currently displaying a map of objects (simple rectangles with text in them, plus some single lines). Unfortunately, the number elements can go up to 25,000, probably even more, which completely crushes the performance. At the moment, we do all the draw calls in the draw() function, which I assume, is the main problem. In an older version, there’s a manual check, if an objec…

---

_[View the full topic](https://discourse.processing.org/t/hardware-solutions-for-long-renders/32370)._
