Repository navigation
Conversation
Contributor
🏷️ CI GuideRuns automatically on every eligible PR before approval:
Heavy model tests:
|
This was referenced Oct 1, 2026
This branch has not been deployed
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
The earlier docs follow-up (#2407) was stacked on the native-MP feature branch and closed when that branch merged. Its remaining timeout clarification is not present on current main.
This one-file follow-up documents the control flow that still exists on main:
lmcache.mp.mq_timeoutbelongs to LMCache adapter message-queue operations;lmcache.mp.lookup_timeoutstarts after lookup submission returns and bounds ATOM's polling loop;lmcache.mp.lookup_poll_intervalcontrols sleeps between polls.Therefore
lookup_timeoutis not a hard wall-clock bound around a blocking adapter submission or status call.No runtime/default/topology behavior changes.
Evidence
The original deterministic CPU characterization is here:
https://github.com/kvnloo/ATOM/actions/runs/36160612338
That run exercised the real lookup facade with a fake adapter/clock and completed 65 MP tests. It demonstrated that submission time is outside the outer lookup polling deadline and that a completed status call is accepted before the next deadline check.
I re-read current main at
922b3519;_MPLookupClient.lookup()still submits first, sets the deadline afterward, then checks adapter status before checking the deadline.No live server/GPU timeout behavior is claimed.
AI-assisted source review and drafting.