fix(brain): calibrate Metal from complete runtime allocations - #50
Merged
Merged
Conversation
Use the Metal working set as the budget basis and allow small-context calibration without first loading the saved hosting profile. Capture indexed MTL allocation tables through process close, require complete measurements, and expose the component costs behind admission decisions.
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.
What changed
MTL0memory breakdown that llama.cpp b11181 emits when the sample server closes. Reject incomplete lines rather than saving a partial measurement.Evidence and limits
MTL0 (Apple M4 Pro)self allocation of 15,714 MiB and a compute buffer of 136.2813 MiB. The existing parser only accepted olderMetal ... buffer size =lines, so calibration rejected the load.