<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Ttft on Gen-AI</title>
    <link>https://gen-ai.fyi/tags/ttft/</link>
    <description>Recent content in Ttft on Gen-AI</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 30 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://gen-ai.fyi/tags/ttft/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Measuring TTFT and TPOT with a Local vLLM Server</title>
      <link>https://gen-ai.fyi/one-layer-down/streaming-vllm-ttft-tpot-colab/</link>
      <pubDate>Sun, 30 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://gen-ai.fyi/one-layer-down/streaming-vllm-ttft-tpot-colab/</guid>
      <description>In the first One Layer Down run, I loaded TinyLlama with vLLM on a Colab T4 and generated 100 tokens. That was useful because it proved the basic path: GPU, CUDA, PyTorch, vLLM, model weights, tokenizer, and one successful generation.
But it was not the latency measurement I actually needed.
When an application calls a model, it can wait for the full answer and show it all at once, or it can stream partial output as the model generates.</description>
    </item>
  </channel>
</rss>
