<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>BitSpeed on SoftDevStudio.com</title>
    <link>https://softdevstudio.com/tags/bitspeed/</link>
    <description>Recent content in BitSpeed on SoftDevStudio.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 20 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://softdevstudio.com/tags/bitspeed/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BitSpeed Joins the Studio With Inspect and Transfer, Two Go Tools for Slow Requests and Broken Uploads</title>
      <link>https://softdevstudio.com/bitspeed-joins-the-studio-with-inspect-and-transfer-two-go-tools-for-slow-requests-and-broken-uploads/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://softdevstudio.com/bitspeed-joins-the-studio-with-inspect-and-transfer-two-go-tools-for-slow-requests-and-broken-uploads/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://bitspeed.org/&#34;&gt;BitSpeed&lt;/a&gt;, the studio&amp;rsquo;s twenty-fourth project, ships two tools that share a name and nothing else at runtime. Each one answers a question that usually ends in guessing: where did this request&amp;rsquo;s time go, and how much of that upload actually made it?&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://bitspeed.org/bitspeed-inspect-explains-http-transfers-and-compares-saved-runs/&#34;&gt;Inspect 0.1.1&lt;/a&gt; records HTTP requests, breaks each one into measured intervals, and says which interval dominated, with every number pointing back to the recorded event it came from. Events that never happened stay unavailable instead of turning into zeros, and the report won&amp;rsquo;t name a server-side cause from client timings alone. Compare two saved runs and it gives medians and ranges per phase, then calls a change inconclusive when the samples overlap. In the &lt;a href=&#34;https://bitspeed.org/bitspeed-inspect-case-study-traces-a-180-ms-slowdown-to-first-byte-wait/&#34;&gt;case study&lt;/a&gt;, a 180 ms drop in first-byte wait clears that bar and two smaller changes don&amp;rsquo;t.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
