Half of them have not written an AI policy
A quarter of incoming pull requests are AI slop. That number travelled everywhere. Two others in the same report matter more if you put open source into a regulated estate.
AI infrastructure below the marketing layer: GPUs, memory, inference, cost per token and what it takes to run it.
A quarter of incoming pull requests are AI slop. That number travelled everywhere. Two others in the same report matter more if you put open source into a regulated estate.
Five stages in the path, and only the last two involve the model. Retrieval is memory bound, generation is GPU bound, and they do not belong on the same hosts.
They implement the same ideas. The difference is what each optimises for and what it costs you to run, which is a less exciting answer than people want.
The arithmetic is easy. The denominator is where models fall apart, and the biggest lever has nothing to do with hardware.
Quantisation is usually framed as a quality tradeoff. The more useful framing is bandwidth, because decode re-reads every weight for every token. Tags: architecture, operations
Passthrough, time-sliced vGPU and MIG do different things to the thing that actually limits you. And fractional slices don't divide capacity the way the spreadsheet says.
Inference behaves like two workloads with opposite requirements, sharing the same silicon. Once you see that, the strange utilisation numbers start making sense.
A single tenant on four GPUs used 37% of the streaming multiprocessors. Four tenants used 71%, with four times the throughput. Same box, no extra hardware.
A four-stage security framework with a scored assessment underneath it. The interesting part isn't the programme, it's the five pillars it scores you against, and the fact that one of them is people.
Two B200 nodes, one liquid-cooled and one air-cooled, 3.2 Tb/s of GPU fabric per node, and a four-host EPYC management domain. This is what the AI Factory announcement looks like when somebody actually builds it.
Six thousand AI-generated patches were tested. A quarter of them fixed the vulnerability without breaking the application. The statistic is the easy part.
The hard part of enterprise AI was never the model. It's letting an agent use enterprise data without giving it access to enterprise data. Tanzu's answer is governed data products published to a marketplace. GA is Fall 2026.