<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chris Newland on foojay.io - Friends Of OpenJDK</title><link>https://foojay.io/today/author/chriswhocodes/</link><description>Articles written by Chris Newland on foojay.io - Friends Of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 27 Jul 2024 10:38:31 +0000</lastBuildDate><atom:link href="https://foojay.io/today/author/chriswhocodes/index.xml" rel="self" type="application/rss+xml"/><item><title>Understanding JVM Memory Layout with OpenJDK24's New PrintMemoryMapAtExit VM Option</title><link>https://foojay.io/today/understanding-jvm-memory-layout-with-openjdk24s-new-printmemorymapatexit-vm-option/</link><pubDate>Sat, 27 Jul 2024 10:38:31 +0000</pubDate><guid>https://foojay.io/today/understanding-jvm-memory-layout-with-openjdk24s-new-printmemorymapatexit-vm-option/</guid><description>&lt;p&gt;&lt;strong&gt;OpenJDK24 recently added a new HotSpot JVM option called &lt;code&gt;PrintMemoryMapAtExit&lt;/code&gt;.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;I know this because I&amp;rsquo;m the maintainer of a project called VMOptionsExplorer, whose job is to track changes to the more than 2000 command line options you can use to control the Java Virtual Machine (JVM).&lt;/p&gt;&#10;&lt;p&gt;VMOptionsExplorer presents this information as a searchable online dictionary of VM options available at &lt;a href="https://chriswhocodes.com" target="_blank" rel="noopener noreferrer"&gt;https://chriswhocodes.com&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;img src="https://foojay.io/today/understanding-jvm-memory-layout-with-openjdk24s-new-printmemorymapatexit-vm-option/vmoe-700x329.png" alt="A screenshot of the VMOptionsExplorer website" width="700" height="329" loading="lazy" decoding="async"&gt;&lt;/p&gt;&#10;&lt;p&gt;The per-JDK option lists are at &lt;a href="https://chriswhocodes.com/vm-options-explorer.html" target="_blank" rel="noopener noreferrer"&gt;https://chriswhocodes.com/vm-options-explorer.html&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Breaking the Code: How Chris Newland is Changing the Game in JVM Performance!</title><link>https://foojay.io/today/breaking-the-code-how-chris-newland-is-changing-the-game-in-jvm-performance/</link><pubDate>Mon, 12 Jun 2023 08:44:27 +0000</pubDate><guid>https://foojay.io/today/breaking-the-code-how-chris-newland-is-changing-the-game-in-jvm-performance/</guid><description>&lt;figure class="alignright size-full is-resized"&gt;&#10; &lt;img src="https://foojay.io/today/breaking-the-code-how-chris-newland-is-changing-the-game-in-jvm-performance/chris.jpg" alt="" width="384" height="384" loading="lazy" class="is-zoomable"&gt;&lt;/figure&gt;&#10;&#10;&lt;p&gt;We&amp;rsquo;re excited to introduce you to Chris Newland, an industry veteran and dedicated JVM performance specialist.&lt;/p&gt;&#10;&lt;p&gt;Chris has a long-standing history of contributing to the Java community with open-source tools aimed at enhancing Java and JVM understanding.&lt;/p&gt;&#10;&lt;p&gt;Among his well-known tools is JITWatch, which has gained significant recognition and use in the JVM community.&lt;/p&gt;&#10;&lt;p&gt;In this conversation, we delve into Chris&amp;rsquo;s journey, his motivations, and his thoughts on JVM performance, Java ecosystem changes, and the role of AI in software development.&lt;/p&gt;</description></item></channel></rss>