Skip to content

Rebase #125 onto main (fine-grained hybrid prefix-cache hits) + diagnostic log - #195

Closed
BadAd84 wants to merge 2 commits into
MiaAI-Lab:mainfrom
BadAd84:pr125-rebased
Closed

BadAd84 wants to merge 2 commits into
MiaAI-Lab:mainfrom
BadAd84:pr125-rebased

Conversation

@BadAd84

@BadAd84 BadAd84 commented Sep 15, 2026

Copy link
Copy Markdown

Rebased version of #125 (by @rwl4) onto current main, resolving the conflicts against 9b9eb13 (per-KV-cache-group APC retention with DFlash SWA replay):

  • Kept main's DFlash SWA replay machinery (BASE_HELPER, INIT/CONVERGE hooks, v3 eagle-verify) and layered Fix fine-grained prefix-cache hits for hybrid GLM KV #125's additive layer on top: FINE_MARK, FINE_OLD/FINE_NEW (filter unsupported_partial_hit_managers by group.kv_cache_spec.participates_in_prefix_caching), three-block idempotent main().
  • Merged the bench (DEFAULT_PAGE_TOKENS = 64 + HEAD's newer /reset_prefix_cache notes) and the README (keeps HEAD's table + reset-route text, adopts the 64-token page-math note).
  • Added a one-shot logger.warning when fine-grained lookup remains disabled by participating managers - on our TP=2 kit the merged overlay applies cleanly but warm hits still land on 4x3584 boundaries, so the log names exactly which manager still blocks 64-token hits on this coordinator build.

Built and boot-tested on 2x GB10 TP=2 (image builds clean through the in-image test suite, incl. test_apc_per_group_retention composition).

rwl4 and others added 2 commits September 15, 2026 23:56
Ignore KV managers that explicitly opt out of prefix caching when deciding whether 64-token hash lookup is safe. KpoolTail remains transient and is rebuilt normally; reusable MLA and Mamba groups still constrain the cache hit.

Keep the overlay additive for images that already contain its earlier DFlash2 hybrid-cache fix, update its patch test, and document the live append-only and semantic validation results.

@plotarmordev plotarmordev left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hold update

Public head checked: 9f3eb7865b0ffe9b9675d0dda4ad89548b8ce2c1.

Why it is held: We need to choose how this rebased version of #125 fits alongside #125 and #171. This is a maintainer choice, not a failed author test.

What we tested: Earlier integrated cache candidates gained reuse on long and medium append requests, but reused fewer tokens on a short append. Those runs were not on this new head, so they do not qualify or reject it. A successful boot is also not proof of cache correctness.

Next action — me, @plotarmordev: Choose the implementation and supported scope, then review and qualify that exact integrated version. Preserve the replay-safety guard and the useful negative cases.

Author action now: None; no new rebase or run requested. If this is selected, the agreed comparison must include cold, repeated, short-append and long-append requests, completed-request cache counters, correct answers, and separate state/numerical checks.

Please keep the hold until the conditions above are met. When a new version is ready for review, include its commit ID, the checks actually run, their results, and anything not tested. Keep failed or incomplete runs in the report. Share only sanitized results—not private prompts, credentials, or machine configuration.

@plotarmordev plotarmordev added merge-hold Do not merge until the stated maintainer dependency or hold is cleared. reviewed Our source review or technical verdict is recorded; not merge approval or runtime qualification. labels Sep 16, 2026
@BadAd84

BadAd84 commented Sep 16, 2026

Copy link
Copy Markdown
Author

Closing - keeping this local; thanks for the context on direction.

@BadAd84 BadAd84 closed this Sep 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-hold Do not merge until the stated maintainer dependency or hold is cleared. reviewed Our source review or technical verdict is recorded; not merge approval or runtime qualification.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants