<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance on Professional developer</title><link>https://www.professionaldev.dev/categories/performance/</link><description>Recent content in Performance on Professional developer</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 04 Apr 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://www.professionaldev.dev/categories/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>What Is Memory Churn and How to Avoid It in Java</title><link>https://www.professionaldev.dev/post/java/memory_churn/</link><pubDate>Tue, 04 Apr 2023 00:00:00 +0000</pubDate><guid>https://www.professionaldev.dev/post/java/memory_churn/</guid><description>
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Modern hardware is very good at predicting the next instructions to be executed. This kind of prediction allows CPUs to do more work in less time. One of the strategies that hardware relies on is data locality. This means that when CPU requests data from main memory, it not only retrieves the requested data, but the hardware also retrieves the data that is stored in proximity to the requested data.&lt;/p&gt;</description></item></channel></rss>