<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Metaspace on Devops Monk</title><link>https://devops-monk.com/tags/metaspace/</link><description>Recent content in Metaspace on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devops-monk.com/tags/metaspace/index.xml" rel="self" type="application/rss+xml"/><item><title>JVM Improvements: Metaspace, PermGen Removal, and Performance</title><link>https://devops-monk.com/tutorials/java8/jvm-improvements/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://devops-monk.com/tutorials/java8/jvm-improvements/</guid><description>PermGen Removal: The End of a Classic Error Before Java 8, the JVM heap was divided into several regions. One of them — Permanent Generation (PermGen) — held class metadata, interned strings, and bytecode. PermGen had a fixed maximum size (defaulting to 64–256 MB depending on the JVM version) and could not grow beyond it.
The result: applications that loaded many classes (frameworks with heavy reflection, dynamic class generation, long-lived application servers) routinely threw:</description></item></channel></rss>