# Hoops Communicator libConverter uses only one CPU core when converting

**URL:** <https://forum.techsoft3d.com/t/hoops-communicator-libconverter-uses-only-one-cpu-core-when-converting/1707>\
**Category:** HOOPS Visualize Web\
**Created:** [March 9, 2023, 7:17am UTC](https://forum.techsoft3d.com/t/hoops-communicator-libconverter-uses-only-one-cpu-core-when-converting/1707 "2023-03-09T07:17:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rui.Zhang03](https://avatars.discourse-cdn.com/v4/letter/r/898d66/32.png) [@Rui.Zhang03](https://forum.techsoft3d.com/u/Rui.Zhang03)\
**Post date:** [March 9, 2023, 7:17am UTC](https://forum.techsoft3d.com/t/hoops-communicator-libconverter-uses-only-one-cpu-core-when-converting/1707/1 "2023-03-09T07:17:49Z")

</div>

Hoops Communicator libConverter uses only one CPU core when converting, resulting in high CPU usage and keeps getting stuck and unable to complete the conversion.Computer configuration with 32 cores,the system is centos7

 ![企业微信截图_16783441758069](https://us1.discourse-cdn.com/flex020/uploads/techsoft3d/original/1X/6069fe2370811b54061e7cf7d3a1a922e5efa106.png)

And when multiple large models are converted concurrently, the system RAM 128G, a single conversion process memory reaches 15G will be automatically killed by the system, return code137  
For large models under centos how to solve this problem

---

<div class="post-metadata">

**Author:** ![gabriel.peragine](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.techsoft3d.com/gabriel.peragine/32/1535_2.png) [@gabriel.peragine](https://forum.techsoft3d.com/u/gabriel.peragine)\
**Post date:** [March 9, 2023, 5:30pm UTC](https://forum.techsoft3d.com/t/hoops-communicator-libconverter-uses-only-one-cpu-core-when-converting/1707/2 "2023-03-09T17:30:40Z")

</div>

Hey Rui,

We’d likely need more context to answer your question properly. I think this might be best for support. I’ll go ahead and open a ticket for you. You’re free to upload your files here as well to see if any other developers have similar issues they’ve solved. My guess is support will be faster, though.
