#Tag

Posts tagged "gpu"

← All posts

  1. Three empty builds before I read the kernel's file

    A per-engine GPU exporter for two consumer Intel Arc cards took five builds in one evening, and the three before the first real row came back empty because each trusted a reading borrowed from somewhere else. The row arrived only after the kernel's own file was read off the working card, which is where any parser for an interface you have not read yourself should start.

  2. My flow named its encoder, and the Intel node paid for it

    A shared Tdarr flow that stored NVENC as its encoder failed on my Intel node with an NVIDIA runtime error. Setting the encoder to auto let each node's probe choose, which fixed my case. Pinning is still a valid choice when you want one specific encoder and every node has it.

  3. The model is an artefact, not a service

    An open-weights model is a file you pull, pin and put on a volume, so it obeys the artefact rules you already run rather than a new discipline called AI operations. The only new budget is VRAM, and the fix for that is unloading the tool the moment nobody is asking it questions.

  4. NVENC and CUDA are different silicon - so share the card

    An LLM and a video transcoder both want a GPU, and the obvious answer is 'buy two.' But a modern GPU isn't one resource - the video encoder is a separate chip from the compute cores. Here's how one RTX 5080 runs local inference and AV1 transcoding at the same time.

  5. Init-gating GPU readiness on Kubernetes

    The single highest-leverage reliability fix for edge GPU workloads: never let an inference pod schedule before the GPU is actually ready.