<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Benchmarking on Pi Stack</title><link>https://www.pistack.xyz/tags/benchmarking/</link><description>Recent content in Benchmarking on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 15 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/benchmarking/index.xml" rel="self" type="application/rss+xml"/><item><title>Self-Hosted Database Benchmarking: pgbench vs sysbench vs HammerDB 2026</title><link>https://www.pistack.xyz/posts/pgbench-sysbench-hammerdb-self-hosted-database-benchmarking-guide-2026/</link><pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/pgbench-sysbench-hammerdb-self-hosted-database-benchmarking-guide-2026/</guid><description>&lt;p>Before you put a database into production, you need to know how it behaves under load. How many queries per second can it sustain? What happens when 500 concurrent connections hit it simultaneously? Does your schema design cause lock contention under write-heavy workloads? Without answering these questions with real benchmark data, you are deploying blind.&lt;/p></description></item></channel></rss>