Urgent.News

What's breaking now, across thousands of outlets.

AI

How to Run an AI Model on Almost Any Hardware: A Practical Guide to Tiny Local LLMs

This month a developer ran a working language model on a Sony PSP-2000. That is a 333 MHz MIPS handheld from 2007 with 64 MB of RAM, and it is streaming English text onto its LCD at one to two tokens per second. The model is Karpathy's stories15M, int8-quantized down to about 17 MB, running on roughly 1,100 lines of pure C. A 64-token completion takes about a minute. I have no plans to buy a PSP,…

This month, a developer successfully ran a language model on a 2007 Sony PSP handheld device. The device has a 333 MHz MIPS processor, 64 MB of RAM, and streams English text at 1-2 tokens per second. The model used is Karpathy's stories15M, int8-quantized down to 17 MB, and runs in around 1,100 lines of pure C code. One token completion takes about a minute to complete.

The author highlights that people often pick a model first, then discover it doesn't fit their hardware. This PSP experiment is an example of running the right hardware-first approach, starting with the available hardware and finding the largest model that fits it with some headroom. The article provides a practical guide to running tiny local LLMs on various hardware.

The trend of smaller models is growing, with notable examples like the PSP build and the Falcon-H1-Tiny 90M family. Quantization has improved for smaller models, with Unsloth Dynamic 3.0 GGUFs achieving up to 10% better top-1 accuracy at the same file size compared to other providers. The author emphasizes that tiny models are not suitable for general chat or agents, but are great for routing and classification, autocomplete, and structured extraction.

To size a model to your hardware in 15 minutes, the author suggests measuring real free memory, budgeting more than the file size, and picking a quant tier based on available memory. For example, UD-Q4_K_XL is suitable for 16 GB machines, UD-Q2_K_XL for 9.83 GB, and UD-IQ1_S for 6.2 GB. The goal is to cover everyday local use cases like chat, tool calling, and light coding without exceeding 500 MB of quantized memory.

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 AI

Declare `tools` Only When Narrowing an APX Agent

Declare tools Only When Narrowing an APX Agent An agent definition should describe a durable role without freezing a temporary snapshot of the runtime around it.

  • Omitting "tools" field preserves broad default allowlist from runtime.
  • Declared "tools" list acts as narrowed allowlist for constrained agents.
  • Remove "tools" field if it's just available tools at agent creation.

Building a $5.70/Month Autonomous AI Coding Agent in the Cloud Using Open-Source Terminal Agent Management

Originally published on tamiz.pro . Introduction Autonomous AI coding agents promise to reduce developer friction by running continuously in the cloud, writing, testing, and refactoring code without…

  • Autonomous AI coding agent costs $5.70/month using open-source tools
  • Ubuntu virtual machine on DigitalOcean or Vultr provides infrastructure
  • Agent-deck and orca enable autonomous coding, testing, and refactoring

More from Sunday 6 September →