Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #2976] [BUG]: Ability to utilize multiple CPU cores #1900

New Issue
Closed
opened 2026-02-22 18:27:08 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:27:08 -05:00
Owner
Copy Link
Copy Source

Originally created by @pmffromspace on GitHub (Jan 15, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2976

How are you running AnythingLLM?

Docker (local)

What happened?

Current Behavior

When running AnythingLLM in Docker, the application appears to only utilize a single CPU core, even when multiple cores are available on the host system. I've noticed this through monitoring container resource usage.

Expected/Desired Behavior

Ability to utilize multiple CPU cores for improved performance, particularly for resource-intensive operations like LLM inference, document processing, or handling multiple concurrent requests.

Questions

  1. Is multi-core utilization already supported, and if so, could you point me to the configuration documentation?
  2. If not currently supported, is this a planned feature for future releases?
  3. Are there any current workarounds or best practices for scaling CPU utilization in production deployments?

Environment

  • Deployment method: Docker
  • Using official Dockerfile from repository
  • Host system has multiple CPU cores available

Additional Context

I've tried standard Docker CPU configuration (--cpus, --cpu-shares) but the application still appears to run on a single core. If this is expected behavior, I'd appreciate understanding the architectural decisions behind this.

Looking forward to your guidance on this matter. Thank you!

Are there known steps to reproduce?

No response

Originally created by @pmffromspace on GitHub (Jan 15, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2976 ### How are you running AnythingLLM? Docker (local) ### What happened? ### Current Behavior When running AnythingLLM in Docker, the application appears to only utilize a single CPU core, even when multiple cores are available on the host system. I've noticed this through monitoring container resource usage. ### Expected/Desired Behavior Ability to utilize multiple CPU cores for improved performance, particularly for resource-intensive operations like LLM inference, document processing, or handling multiple concurrent requests. ### Questions 1. Is multi-core utilization already supported, and if so, could you point me to the configuration documentation? 2. If not currently supported, is this a planned feature for future releases? 3. Are there any current workarounds or best practices for scaling CPU utilization in production deployments? ### Environment - Deployment method: Docker - Using official Dockerfile from repository - Host system has multiple CPU cores available ### Additional Context I've tried standard Docker CPU configuration (--cpus, --cpu-shares) but the application still appears to run on a single core. If this is expected behavior, I'd appreciate understanding the architectural decisions behind this. Looking forward to your guidance on this matter. Thank you! ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:27:08 -05:00
yindo closed this issue 2026-02-22 18:27:08 -05:00
yindo commented 2026-02-22 18:27:08 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jan 15, 2025):

NodeJS is single threaded, even if multiple cores are available the language itself only uses 1 core. The only way around this is to re-arch some subservices into worker_threads or leveraging cluster

@timothycarambat commented on GitHub (Jan 15, 2025): NodeJS is single threaded, even if multiple cores are available the language itself only uses 1 core. The only way around this is to re-arch some subservices into `worker_threads` or leveraging `cluster`
yindo changed title from [BUG]: Ability to utilize multiple CPU cores to [GH-ISSUE #2976] [BUG]: Ability to utilize multiple CPU cores 2026-06-05 14:43:21 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1900
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?