Skip to content

Habitat-Sim only utilizes first 64 logical CPUs #2581

@yichenzeng24

Description

@yichenzeng24

Habitat-Sim version

v0.2.2

Habitat is under active development, and we advise users to restrict themselves to stable releases. Are you using the latest release version of Habitat-Sim? Your question may already be addressed in the latest version. We may also not be able to help with problems in earlier versions because they sometimes lack the more verbose logging needed for debugging.

Main branch contains 'bleeding edge' code and should be used at your own risk.

Docs and Tutorials

Did you read the docs? https://aihabitat.org/docs/habitat-sim/

Did you check out the tutorials? https://aihabitat.org/tutorial/2020/

Perhaps your question is answered there. If not, carry on!

❓ Questions and Help

I'm using habitat-sim==v0.2.2 to perform audio simulations (using the integrated acoustic simulation in SoundSpaces pipeline). However, the simulation is very CPU-intensive, and I want to accelerate it using all available CPU threads on my server.

No matter what I try, Habitat-Sim never uses more than 50% CPU. I opened htop and observed that the process only uses logical CPUs 0-63. The other half (64-127) is completely idle.

I tried the following:
taskset -c 0-127 python my_script.py
taskset -c 64-127 python my_script.py
numactl --physcpubind=0-127 --interleave=all python my_script.py
But Habitat-Sim still only utilizes cores 0–63. Even when I restrict it to 64-127 via taskset, it still spawns threads on 0–63 only.

Platform: Dual-socket server, 2 CPUs, each with 32 cores / 64 threads (total 128 logical cores)
NUMA layout:
NUMA node(s): 2
NUMA node0 CPU(s): 0-31,64-95
NUMA node1 CPU(s): 32-63,96-127

How can I configure Habitat-Sim to utilize all 128 logical CPUs (0–127) across both NUMA nodes for audio simulation?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions