<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Classification on Christian Hotz-Behofsits</title><link>https://hotzbehofsits.com/tags/classification/</link><description>Recent content in Classification on Christian Hotz-Behofsits</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 28 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://hotzbehofsits.com/tags/classification/index.xml" rel="self" type="application/rss+xml"/><item><title>Running a Zero-Shot Classifier on Your Own GPU</title><link>https://hotzbehofsits.com/post/local_llm_inference/</link><pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate><guid>https://hotzbehofsits.com/post/local_llm_inference/</guid><description>&lt;p&gt;In a recent project I had 1,500 tweets and a codebook with 16 categories. There were three ways to get labels: code them by hand, send them to a commercial API, or run an open-weight model on our own GPU. I went with the third one, and this post is what I wish someone had told me before I started.&lt;/p&gt;
&lt;p&gt;The reasons for staying local are not ideological. First, the data never leaves the machine. Second, I have already the hardware and there is no per-token cost, so you can iterate on the prompt fifty times instead of five, and prompt iteration is where the accuracy comes from. Third, a pinned model version at &lt;code&gt;temperature=0&lt;/code&gt; is reproducible, which turns the classification step into something you can ship in a replication package rather than a black box you apologize for in a footnote.&lt;/p&gt;</description></item></channel></rss>