<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Testing on RollupDB.com</title>
    <link>https://rollupdb.com/tags/testing/</link>
    <description>Recent content in Testing on RollupDB.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 17 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rollupdb.com/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How RollupDB Was Tested With Killed Processes and an Outside Reference</title>
      <link>https://rollupdb.com/how-rollupdb-was-tested-with-killed-processes-and-an-outside-reference/</link>
      <pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rollupdb.com/how-rollupdb-was-tested-with-killed-processes-and-an-outside-reference/</guid>
      <description>&lt;p&gt;A database that throws data away on purpose had better be right about what it keeps. So RollupDB&amp;rsquo;s tests ask two questions over and over. Is the answer the same one you&amp;rsquo;d get from every raw reading? And does a write that was acknowledged survive the process dying, while one that wasn&amp;rsquo;t leaves no trace?&lt;/p&gt;&#xA;&lt;p&gt;All the numbers below come from one recorded run on a 4-CPU Linux machine in GitHub&amp;rsquo;s runners, Go 1.27.2. The script that made them and its full output are in the repository&amp;rsquo;s &lt;a href=&#34;https://github.com/rollupdb/rollupdb/tree/main/test/results&#34;&gt;test/results folder&lt;/a&gt;, so anyone can run it again and compare.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
