<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Load Shedding on Nalar</title>
    <link>https://nalar.dev/tags/load-shedding/</link>
    <description>Recent content in Load Shedding on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 12 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/load-shedding/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Load Shedding: Reject Work Before Overload Spreads</title>
      <link>https://nalar.dev/load-shedding-reject-work-before-overload-spreads/</link>
      <pubDate>Sat, 12 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/load-shedding-reject-work-before-overload-spreads/</guid>
      <description>&lt;h1 id=&#34;load-shedding-reject-work-before-overload-spreads&#34;&gt;Load Shedding: Reject Work Before Overload Spreads&lt;/h1&gt;&#xA;&lt;p&gt;A service has finite capacity. When offered work exceeds that capacity for long enough, accepting every request can make the service less useful rather than more useful. Queues grow, deadlines expire, memory pressure rises, dependencies receive more traffic, and successful throughput can fall.&lt;/p&gt;&#xA;&lt;p&gt;Load shedding is the deliberate rejection of work that the system cannot serve within an acceptable budget. The goal is not to maximize the number of requests admitted. The goal is to preserve useful service during overload.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
