<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Summarization on Nalar</title>
    <link>https://nalar.dev/tags/summarization/</link>
    <description>Recent content in Summarization on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/summarization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Where PEGASUS-XSum Inference Time Goes</title>
      <link>https://nalar.dev/where-pegasus-xsum-inference-time-goes/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/where-pegasus-xsum-inference-time-goes/</guid>
      <description>&lt;p&gt;&lt;code&gt;google/pegasus-xsum&lt;/code&gt; is a summarization checkpoint, not a compact text utility. Its latency follows directly from the work performed by a large Transformer encoder-decoder: first encode the source document, then run the decoder repeatedly until the summary is complete. On a CPU, the second phase is usually the part that makes a short output feel disproportionately expensive.&lt;/p&gt;&#xA;&lt;p&gt;The original PEGASUS work describes a Transformer encoder-decoder pretrained with Gap Sentences Generation and reports a 568M-parameter best model. The XSum checkpoint is fine-tuned for highly abstractive single-document summarization. That combination is useful when summary quality matters, but it also means inference has substantially more machinery than extracting a few source sentences or running a small classifier.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
