<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>certstream-server-rust</title>
        <link>https://certstream.dev/blog/</link>
        <atom:link href="https://certstream.dev/feed.xml" rel="self" type="application/rss+xml"/>
        <description>Engineering write-ups from building a Certificate Transparency streaming server in Rust.</description>
        <language>en</language>
        <lastBuildDate>Tue, 25 Aug 2026 20:43:46 +0000</lastBuildDate>
        <item>
            <title>I blamed HTTP/2 multiplexing. Then I counted the connections.</title>
            <link>https://certstream.dev/blog/http2-multiplexing-vs-per-connection-rate-limits.html</link>
            <guid isPermaLink="true">https://certstream.dev/blog/http2-multiplexing-vs-per-connection-rate-limits.html</guid>
            <pubDate>Tue, 25 Aug 2026 09:00:00 +0000</pubDate>
            <description>Six CT logs were falling behind. HTTP/2 multiplexes every request onto one connection, so we pinned the operator to HTTP/1.1 and got three connections instead of one. Throughput did not move: 49.0 vs 50.0 entries a second. The real limit was 29 entries returned for a 1024-entry request.</description>
        </item>
        <item>
            <title>The CT logs that serve tiles but publish no checkpoint</title>
            <link>https://certstream.dev/blog/ct-logs-tiles-without-checkpoint.html</link>
            <guid isPermaLink="true">https://certstream.dev/blog/ct-logs-tiles-without-checkpoint.html</guid>
            <pubDate>Tue, 25 Aug 2026 09:00:00 +0000</pubDate>
            <description>Three CT logs were falling 279,000 entries behind with zero errors. They serve static-ct-api tiles but return 404 for /checkpoint. Reading them with the tree size from get-sth, and the three failures that only appeared against live logs.</description>
        </item>
        <item>
            <title>358 MB resident, 52 MB in use: where the rest went</title>
            <link>https://certstream.dev/blog/jemalloc-transparent-huge-pages-rss.html</link>
            <guid isPermaLink="true">https://certstream.dev/blog/jemalloc-transparent-huge-pages-rss.html</guid>
            <pubDate>Tue, 25 Aug 2026 09:00:00 +0000</pubDate>
            <description>A Rust service looked like it was leaking: 358 MB resident against a 52 MB live heap. Transparent huge pages were holding 206 MB jemalloc could not return, and the fix was five settings the allocator had been running without.</description>
        </item>
    </channel>
</rss>
