liveBook · Manning

Native executable

As explained in The Art of Code

Native execution runs compiled program code directly for a target operating-system and processor platform without an intermediate virtual-machine execution layer.

A native executable runs compiled code directly for a target operating-system and processor platform, avoiding an intermediate virtual-machine execution layer. This can reduce startup time, memory usage, and CPU work, though it gives up some portability. section 8.4.5

Compiling Java ahead of time

Java normally runs on a virtual machine. GraalVM Native Image can instead compile a Java application ahead of time into a platform-specific executable, removing runtime abstraction layers and reducing execution overhead. section 8.4.5

Use native compilation when the efficiency gains justify platform-specific output:

  • Reduce startup time, memory usage, and CPU work. section 8.4.5
  • Balance efficiency against the portability provided by a virtual machine. section 8.4.5

How The Art of Code covers it

How deep it goes
Explains direct execution, platform-specific compilation, and resource effects without detailing compiler internals.
Examples
Uses Java applications compiled by GraalVM Native Image into platform-specific executables.
What it assumes
Assumes familiarity with Java and distinguishes virtual-machine execution from direct native execution.
What you can do after
Evaluate when platform-specific native compilation can reduce startup, memory, and CPU costs.
How it connects
Connects native executables with Java, virtual machines, GraalVM Native Image, portability, and ahead-of-time compilation.

Also explained in

Compare how 4 books explain native executable →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of The Art of Code. The section links point to the parts of the book it draws on.