You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -154,6 +153,14 @@ Debug info is also generated as part of this stage (if requested).
154
153
The code area contains machine code produced by the Graal compiler for all reachable methods.
155
154
Therefore, reducing the number of [reachable methods](#glossary-reachability) also reduces the size of the code area.
156
155
156
+
##### <a name="glossary-code-area-origins"></a>Origins of Code Area
157
+
To help users understand where the machine code of the code area comes from, the build output shows a breakdown of the top origins.
158
+
An origin is a group of Java sources and can be a JAR file, a package name, or a class name, depending on the information available.
159
+
The [`java.base` module](https://docs.oracle.com/en/java/javase/17/docs/api/java.base/module-summary.html), for example, contains base classes from the JDK.
160
+
The `svm.jar` file, the `org.graalvm.nativeimage.base` module, and similar origins contain internal sources for the Native Image runtime.
161
+
To reduce the size of the code area and with that, the total size of the native executable, re-evaluate the dependencies of your application based on the code area breakdown.
162
+
Some libraries and frameworks are better prepared for Native Image than others, and newer versions of a library or framework may improve (or worsen) their code footprint.
163
+
157
164
#### <a name="glossary-image-heap"></a>Image Heap
158
165
The heap contains reachable objects such as static application data, metadata, and `byte[]`for different purposes (see below).
0 commit comments