fix(worker): report RAM alongside GPU memory - #11167
Merged
Merged
Conversation
Owner
|
@localai-org-maint-bot surface this in the UI as well |
Assisted-by: Codex:gpt-5
localai-org-maint-bot
force-pushed
the
bot/issue-11051-available-ram-sdd
branch
from
July 28, 2026 18:03
12b60ee to
9c1b0c0
Compare
Assisted-by: Codex:gpt-5
Collaborator
Author
|
Done in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
available_ramon every heartbeat so GPU detection changes cannot leave a stale RAM metricFixes #11051
Testing
go test -count=1 ./core/services/workergit diff --check HEAD^ HEADDocumentation
Updated
docs/content/features/distributed-mode.mdto explain independent RAM/VRAM reporting and unified-memory behavior.