<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Benchmarks on KvSQL.com</title>
    <link>https://kvsql.com/tags/benchmarks/</link>
    <description>Recent content in Benchmarks on KvSQL.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 22 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://kvsql.com/tags/benchmarks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>KvSQL Against SQLite on the Same Machine: Key Reads, SQL Reads and Synced Commits</title>
      <link>https://kvsql.com/kvsql-against-sqlite-on-the-same-machine-key-reads-sql-reads-and-synced-commits/</link>
      <pubDate>Thu, 22 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://kvsql.com/kvsql-against-sqlite-on-the-same-machine-key-reads-sql-reads-and-synced-commits/</guid>
      <description>&lt;p&gt;KvSQL&amp;rsquo;s claim is a fast path by key that skips the SQL machinery, on the same records SQL reads. A claim like that needs a measurement, and the obvious yardstick is SQLite. It&amp;rsquo;s the most used embedded database there is, and it&amp;rsquo;s very good. So the project&amp;rsquo;s test script runs a benchmark against SQLite every time it records results, and saves it next to the test output.&lt;/p&gt;&#xA;&lt;p&gt;The figures here are from the recorded run of October 22, 2026, on a Linux container with two virtual CPUs. The full table, with every condition, is &lt;a href=&#34;https://github.com/softdevstudio/kvsql/blob/main/test/results/latest/bench.md&#34;&gt;bench.md&lt;/a&gt; in the repository. A container like this is noisy: between runs on the same day, single figures moved by 20 to 30 percent. Treat the gaps below as rough sizes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
