# BEAM on 128-core Linux box seeming not to use many of available cores

**URL:** <https://erlangforums.com/t/beam-on-128-core-linux-box-seeming-not-to-use-many-of-available-cores/3858>\
**Category:** Questions / Help\
**Tags:** macos, linux, beam, performance, erlang\
**Created:** [July 23, 2024, 10:45pm UTC](https://erlangforums.com/t/beam-on-128-core-linux-box-seeming-not-to-use-many-of-available-cores/3858 "2024-07-23T22:45:47Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![YurikoDiaz](https://erlangforums.com/letter_avatar_proxy/v4/letter/y/f6c823/32.png) [@YurikoDiaz](https://erlangforums.com/u/YurikoDiaz)\
**Post date:** [July 29, 2026, 3:44pm UTC](https://erlangforums.com/t/beam-on-128-core-linux-box-seeming-not-to-use-many-of-available-cores/3858/21 "2026-07-29T15:44:42Z")

</div>

The super-carrier + MMscs combo helps with that memory allocation noise. I’d also look at scheduler binding though — on 128 cores the default placement can lead to a lot of thread bouncing between cores, which compounds the context switching problem. Worth looking into if you haven’t already.

---

<div class="post-metadata">

**Author:** ![starbelly](https://erlangforums.com/user_avatar/erlangforums.com/starbelly/32/209_2.png) [@starbelly](https://erlangforums.com/u/starbelly)\
**Post date:** [August 13, 2026, 2:05am UTC](https://erlangforums.com/t/beam-on-128-core-linux-box-seeming-not-to-use-many-of-available-cores/3858/22 "2026-08-13T02:05:25Z")

</div>

Right, definitely have some custom settings where I’m at in this regard 😃

This turned out to be an instrumentation problem. Just about all cores running at 99%, no high sys load, abnormal context switching, etc, just happily doing a bunch of work during peak load time (re-hydration).

[Previous page](https://erlangforums.com/t/beam-on-128-core-linux-box-seeming-not-to-use-many-of-available-cores/3858.md?page=1)