# SharedArrayBuffer eats up 100% CPU

**URL:** <https://devforum.zoom.us/t/sharedarraybuffer-eats-up-100-cpu/102758>\
**Category:** Video SDK\
**Created:** [January 29, 2024, 9:01pm UTC](https://devforum.zoom.us/t/sharedarraybuffer-eats-up-100-cpu/102758 "2024-01-29T21:01:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![akai](https://avatars.discourse-cdn.com/v4/letter/a/2bfe46/32.png) [@akai](https://devforum.zoom.us/u/akai)\
**Post date:** [January 29, 2024, 9:01pm UTC](https://devforum.zoom.us/t/sharedarraybuffer-eats-up-100-cpu/102758/1 "2024-01-29T21:01:47Z")

</div>

**Video SDK Type and Version**  
Node.js @zoom/videosdk 1.10.5

**Description**  
We are recently migrating from a flawlessly working Twilio Video solution. Our needs require large rooms and thus its imperative to use the ShareArrayBuffer solution. The Zoom solution works fine on newer computers but anything 4 years or older almost comes to a halt with both CPU & Memory climbing up to 100%.

Is there an easy way to detect computers that Zoom SDK can’t encode/decode easily on? These computers all have WebGL enabled and return true for isSupportMultipleVideos().

We never noticed such issues with Twilio Video or Janus based WebRTC video rooms which makes us believe that the underlying implementation of Zoom Video SDK is relying on inefficient encoding/decoding algorithms.

**Error?**  
Sluggish, grainy CPU hog.

---

<div class="post-metadata">

**Author:** ![seth.wang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/seth.wang/32/56069_2.png) [@seth.wang](https://devforum.zoom.us/u/seth.wang)\
**Post date:** [January 30, 2024, 5:29am UTC](https://devforum.zoom.us/t/sharedarraybuffer-eats-up-100-cpu/102758/2 "2024-01-30T05:29:53Z")

</div>

Thanks for your feedback.

Can you provide the device and the browser version?

---

<div class="post-metadata">

**Author:** ![akai](https://avatars.discourse-cdn.com/v4/letter/a/2bfe46/32.png) [@akai](https://devforum.zoom.us/u/akai)\
**Post date:** [January 30, 2024, 4:21pm UTC](https://devforum.zoom.us/t/sharedarraybuffer-eats-up-100-cpu/102758/3 "2024-01-30T16:21:14Z")

</div>

Thanks for the follow up, Seth.

This is a device with Windows 10 Pro 22H2 with Chrome 121.0.6167.86 (64bit).

Del Latitude 5510, CPU 1.60 ghz 2.11 ghs, 8gb Ram, 64 bit processor

---

<div class="post-metadata">

**Author:** ![sam9](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@sam9](https://devforum.zoom.us/u/sam9)\
**Post date:** [May 6, 2024, 5:13pm UTC](https://devforum.zoom.us/t/sharedarraybuffer-eats-up-100-cpu/102758/5 "2024-05-06T17:13:49Z")

</div>

Did you find any solutions for this? I’m noticing the same issue