<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Graalvm on Anttu&#39;s Blog</title>
		<link>https://anTtutu.github.io/tags/graalvm/</link>
		<description>Recent content in Graalvm on Anttu&#39;s Blog</description>
		<generator>Hugo</generator>
		<language>zh-CN</language>
		
		
		
		
			<lastBuildDate>Thu, 18 Sep 2025 08:00:00 +0800</lastBuildDate>
		
			<atom:link href="https://anTtutu.github.io/tags/graalvm/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>GraalVM与Native Image详解：原理、Spring Boot样例与编译/运行镜像选型</title>
				<link>https://anTtutu.github.io/post/2025-09-18-graalvm-native-image/</link>
				<pubDate>Thu, 18 Sep 2025 08:00:00 +0800</pubDate>
				<guid>https://anTtutu.github.io/post/2025-09-18-graalvm-native-image/</guid>
				<description>&lt;h2 id=&#34;前言&#34;&gt;前言&lt;/h2&gt;&#xA;&lt;p&gt;Java 应用启动慢、吃内存、还要预热，放在 Serverless 和弹性伸缩的场景里很难受。GraalVM 的 Native Image 用 AOT 编译解决了这个问题：毫秒启动、内存省一半、连 JVM 都不要了。代价是反射要登记、构建要等几分钟、生态要适配。这篇把原理讲清、把 Spring Boot 3 的样例跑通，重点记录一下我在容器化时踩坑最多的部分：编译镜像和运行镜像怎么选。&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
