<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Slow on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/slow/</link><description>Recent content in Slow on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 29 Jan 2026 07:00:02 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/slow/index.xml" rel="self" type="application/rss+xml"/><item><title>Houston, we have problems with the queries</title><link>https://javapro-en.svenruppert.com/houston-we-have-problems-with-the-queries/</link><pubDate>Thu, 29 Jan 2026 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/houston-we-have-problems-with-the-queries/</guid><description>&lt;h2 id="introduction"&gt;introduction&lt;/h2&gt;
&lt;p&gt;Most developers build queries to access a relational database, using some ORM in different ways to generate the query automatically or write the query manually. Everything could work in most cases in other environments, but at some point, the query becomes slow, or the application takes more time to execute the same task that it did in the past. At this point, the developers, QA, and many others waste a lot of time understanding the change that produced the problem in the last commits, but why not create a test that detects some issues with performance before they appear?&lt;/p&gt;</description></item></channel></rss>