Urgent.News

What's breaking now, across thousands of outlets.

Tech

The Cheapest CUDA GPU on AWS Has an Arm CPU — and You Probably Want the Intel One

This article provides a step by step deployment guide for Gemma 4 E2B onto the two cheapest whole GPU CUDA instances AWS sells, and compares what they cost to run. A suite of Python MCP tools is built to simplify management of the vLLM hosted deployment. Everything was measured on 2026-08-30. What is this project trying to Do? The question is simple: if you want a CUDA GPU on AWS as cheaply as…

The article explains how to deploy Gemma 4 E2B onto the two cheapest whole GPU CUDA instances AWS sells, comparing their costs. The two instances are G5g and G4dn, both with NVIDIA T4 GPUs, but they differ in their host CPUs. G5g uses a Graviton2 (Arm) host, while G4dn uses an Intel host. The article concludes that the cheapest real CUDA GPU on AWS is an Arm box, which is 20% cheaper per hour on demand and 59% cheaper on spot.

However, the rest of the article reveals that the host CPU determines which kernels you get, making the choice between the two instances dependent on whether you're buying hours or tokens.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Gemma 4 in Pure JAX: What Changes Between Turing and Ada, and What Doesn't

This article is a measurement report on running a hand-written Gemma 4 port in pure JAX across two NVIDIA GPUs a generation apart, and on the two places the "it's just JAX" abstraction leaks.

  • Gemma 4 port runs in pure JAX on Turing and Ada GPUs
  • Compute dtype policy sets bfloat16 on both GPUs, causing performance hit on Turing
  • KV ring cache bug due to irregular Gemma 4 geometry prevents optimal port performance

g5g vs g6 for LLM Serving: the Same Code, and 3.7x the Throughput

This article compares two AWS GPU instance families for serving a small language model, using a payload that is byte-identical on both.

  • g5g.2xlarge and g6.2xlarge instances compared for LLM serving
  • g6.2xlarge shows 3.7x higher throughput than g5g.2xlarge
  • g5g suffers 87% decode-to-dtype conversion bottleneck

The Phishing Site Tried to Talk to My AI. That Became the Evidence.

I wrote this piece for the purposes of entering Google's All Things Agentic Hackathon (Fortified Enterprise Fleet track).

  • Phishing site used Unicode Tag Characters to communicate with AI
  • AI instructed to ignore previous rules, redirect report
  • System designed to minimize false negatives while limiting false positives

More from Monday 31 August →