NVIDIA puts $3.5B into MediaTek, and it's not a rescue

NVIDIA puts $3.5B into MediaTek, and it's not a rescue

Good morning ๐Ÿ‘‹ NVIDIA just wrote a $3.5 billion check to a company it doesn't need to rescue. The reason why says more about where NVIDIA thinks AI is headed than the number does.

In today's issue:

Get tomorrow's issue in your inbox.

One concise AI brief, sent after the signal clears the noise.


๐Ÿ”ญ THE ONE THING

๐Ÿค NVIDIA puts $3.5B into MediaTek, and it's not a rescue

NVIDIA is investing $3.5 billion in convertible bonds issued by MediaTek, tying the two chipmakers together across NVLink Fusion custom silicon, the RTX and DGX Spark PC lineup, and Dimensity Auto chips for software-defined vehicles. Jensen Huang framed it as AI moving from "the world's largest AI factories" down to the PC and the car, which is the real subtext: NVIDIA wants its interconnect and memory stack under every device class MediaTek already ships at volume. For MediaTek, the bonds are cheap capital and a seat at NVIDIA's roadmap instead of a fight against it. Convertible bonds also mean NVIDIA could end up holding MediaTek equity down the line, so the conversion price is worth watching once it's disclosed.


๐Ÿง  MODELS & RELEASES


๐Ÿ”ฌ RESEARCH HIGHLIGHTS


๐Ÿ›๏ธ POLICY & REGULATION


๐Ÿ› ๏ธ TRY THIS

Stop paying for idle GPU on every inference request

AWS just published the numbers: running speech-recognition models one-process-per-GPU on EC2 wastes most of the card, since a single ASR request rarely touches the full compute budget. NVIDIA's CUDA Multi-Process Service, paired with Triton Inference Server, lets multiple model processes share one GPU instead of each claiming its own. AWS cut GPU infrastructure spend 75% this way while holding sub-second latency. Worth pulling that lever now, given how much deeper NVIDIA is wiring itself into the stack (see the MediaTek money above).

1. Profile GPU utilization per inference request on your current fleet. Anything well under 100% is money left on the table.

2. Turn on CUDA MPS on your EC2 GPU instances and pack several Triton model instances onto each GPU instead of one-per-card.

3. Re-run load tests at real production traffic and check latency holds before you touch instance count.

4. Right-size the fleet down once latency checks out, and bank the savings.

Prompt: Write a Triton Inference Server deployment config for an EC2 GPU instance with NVIDIA CUDA MPS enabled, running multiple ASR model instances on a single GPU, plus a load-test checklist to confirm sub-second p99 latency before shrinking the fleet.

Worth a look


๐Ÿ”— QUICK LINKS


See you tomorrow.

Pradeep Perugu

Get inovAIte in your inbox.