✎Blog

Blog

Notas de los proyectos de AMARBARO: resultados medidos, el protocolo bajo el que se midieron, y las predicciones que resultaron incorrectas.

Más recientes Agentes y herramientas 6 min de lectura

Twelve Ideas That Did Not Help

Twelve network ideas tied, lost or starved against plain search or their control, with the counts for each. Five had a prereg file. The failures in our measuring that we caught are listed beside them.

Leer →
Measurement 6 min

The Bottleneck Was the PCIe Link, Not the Code

GPU idle was 60 percent of decode wall time, and the largest share was host-to-device copies running at 3.1 to 3.4 GB/s against 28.5 GB/s on a healthy boot. The root port negotiated 2.5 GT/s. Several timed A/Bs from that boot are void, one fusion ratio survives, and the machine is still on the slow link.

GPU kernels 8 min

Same Bits on the CPU and the GPU

Std.math exp disagreed between the CPU and the GPU on 19,437 of 40,017 inputs. A shared exp written with explicit fma matched on all 40,017, at 3.6 times the cost in an exp-bound kernel. One attention layer then matched bit for bit, and a float Freivalds certificate caught every planted fault.

Practice 7 min

372 Math Papers, Zero Engine Features

Three model passes over one-line index rows flagged four families. Each failed against the operators the engine actually runs. The screen yielded no engine feature, and the four vero claims and the Float64 log fix both predate it.

Measurement 6 min

The profiler crashed because the CPU has a GPU

Four days of a wrong verdict ("unusable with our Mojo kernels") ended when we unbound the integrated GPU. A plain kernel then read SQ_WAVES 32,768 exactly, and a second fault, counters reading zero, came out from behind the first.

Practice 7 min

The GPU Is a Queue

A day with 142 GPU jobs and 34 failures, and a week of incidents that never needed the GPU to find. The fix is not a faster GPU, it's treating the card as a shared, budgeted resource with a preflight step before anything touches it.

Agents & tooling 8 min

The IPC Primitive Is a Latent Tensor

An OS design in which the message between agents is a latent tensor with an identity, and text is one adapter among several. The transport and tiering numbers are real, the fork gate is resolved, and the thesis experiment failed. That experiment asked whether an untrained model reads its own hidden states as reasoning; in the rerun, it did not.