<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>8 Years of Optimizing Apache Otava: How disconnected open source developers took an algorithm from n3 to constant time · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2505.06758/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2505.06758/feed.xml" rel="self" type="application/rss+xml" /><item><title>8 Years of Optimizing Apache Otava: How disconnected open source developers took an algorithm from n3 to constant time — mentioned by homarp</title><link>https://news.ycombinator.com/item?id=47281430</link><guid isPermaLink="false">urn:hackerpapers:mention:2505.06758:47281430</guid><pubDate>Fri, 06 Mar 2026 21:39:12 GMT</pubDate><description>&lt;p&gt;Change Detection for Continuous Performance Engineering: Otava performs statistical analysis of performance test results stored in CSV files, PostgreSQL, BigQuery, or Graphite database. It finds change-points and notifies about possible performance regressions. You can also read &amp;quot;8 Years of Optimizing Apache Otava: How disconnected open source developers took an algorithm from n3 to constant time&amp;quot; - https://arxiv.org/abs/2505.06758v1 and &amp;quot;The Use of Change Point Detection to Identify Software Performance Regressions in a Continuous Integration System&amp;quot; - https://arxiv.org/abs/2003.00584 (and I…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2505.06758/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PF</category></item></channel></rss>
