Skip to content

fix(qa): ollama_parity cannot measure on unified memory, ollama stays resident while apr plans its GPU load #5302

Closed as not planned

Description

@noahgift

apr qa --ollama-from-file on the 8 GB unified-memory Orin (runner label jetson) fails the ollama_parity gate without measuring: ollama's import is resident while apr plans its GPU load, so apr refuses on capacity:

ollama_parity could not run: ... GPU capacity refused: ... weights 1211 MiB + KV 3 MiB + workspace 137 MiB + overhead 512 MiB = 1863 MiB, against 1134 MiB free of 5706 MiB (unified memory: MemAvailable 3036 MiB less a 1902 MiB headroom ...)

On a unified-memory device the two engines share one pool, so the gate must measure them one after the other (unload ollama, keep_alive: 0, before apr loads), or the parity row never exists on edge devices. Model Qwen3.5-2B-Q4_K_M.gguf, apr 0.71.2 at #5292 head cebe27dc.

Done when the edge nightly's ollama parity row is measured on this device.

Refs #5254.

Activity

  1. noahgift commented on Oct 14, 2026

    @noahgift
    MemberAuthor

    merged into #5305 (master ticket for epic #3598; triage rule 7b, 2026-10-14). It is a checklist row there; reopen this issue when work on it starts or its PR opens.

  2. noahgift commented on Oct 14, 2026

    @noahgift
    MemberAuthor

    Moved: this sub-ticket is now a row in #5321 (apr memory footprint: serve Qwen3.5 within 8 GB unified-memory ARM64 CUDA (Orin)), split out of #5305 by theme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions