<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Yestino - The Signal · Benchmarking</title><link>https://yestino.com/entities/benchmarking-151169</link><description>Every event involving Benchmarking</description><language>en</language><atom:link href="https://yestino.com/entities/benchmarking-151169/feed.xml" rel="self" type="application/rss+xml"/><item><title>Tuning a Server for Benchmarking</title><link>https://yestino.com/events/tuning-a-server-for-benchmarking-466a4c</link><guid isPermaLink="true">https://yestino.com/events/tuning-a-server-for-benchmarking-466a4c</guid><pubDate>Sat, 26 Sep 2026 11:48:40 GMT</pubDate><description>Optimizing code starts with measuring it, and a measurement is only useful if it is repeatable: a 2% improvement is invisible under 5% of noise.
Sources: Lobsters</description></item></channel></rss>