Back to Zing Documentation Home
The Zing Runtime for Java is a JDK that implements the umbrella Java Specification Request (JSR) for applicable Java Platform, Standard Edition (Java SE) versions (for example, JSR 336 for Java SE 7); and constitutes a “Compliant Implementation” under the specification licenses for the final release umbrella JSR specifications that Zing implements.
Zing includes dynamic “just-in-time” (JIT) compiler technologies that adaptively compile Java bytecodes into optimized machine instructions, and manages the Java heap using Garbage Collector technology developed by Azul Systems.
Zing is supported on a variety of Linux distributions and x64 processor architectures. A current list of supported Linux operating systems and x64 architecture CPUs is covered in the remaining chapters and Release Notes.
A complete list of applicable Java SE JSRs can be found here:
For Java SE 7 (JSR 336): https://jcp.org/en/jsr/detail?id=336
For Java SE 8 (JSR 337): https://jcp.org/en/jsr/detail?id=337
For Java SE 11 (JSR 384): https://jcp.org/en/jsr/detail?id=384
For Java SE 13 (JSR 388): https://jcp.org/en/jsr/detail?id=388
Each of the Zing components are installed on machines relative to the ZVM host machine, as listed.
ZVM and ZST are installed on the same machine. ZVM requires ZST to use the Zing memory management features. The ZVM package software is packaged as standard .sh, .tar.gz, .rpm, or .deb. The ZST package software is packaged as standard .rpm or .deb.
Starting with ZVM 19.07.0.0, ZST is not required. See
Zing System Requirementsfor details.
Zing license file is installed on the ZVM host.
Zing Pool license server is installed on a separate machine from the ZVM host machines that will be in its license pool. It is a Java application and requires a JVM instance to run. The Pool license server offers flexibility in allocating Zing licenses and it is optional. The Zing Pool license server is packaged as a .sh. A specific Pool license contract with Azul is required to use this option.
ZVision and ZVRobot are the profiling and diagnostics tools for the ZVM processes. They are automatically installed with the ZVM component.
This section lists system requirements for operating systems supported by Zing in the Zing Virtual Machine with Zing System Tools mode of operation.
The components ZVM and ZST can be installed on machines running the following operating systems using
.deb installers, as appropriate:
|RHEL/CentOS||6, 7, 8|
|Oracle Linux Server||6, 7|
|SLES||12 (SP1, SP2, SP3)|
|Ubuntu||16.04 - 20.04|
|Debian||9 (Stretch) and 10 (Buster)|
|Amazon Linux||1, 2|
The Zing components ZVM, ZST, and the Pool license server can be installed on machines running the following CPU types.
- 64-bit x86 CPUs
Intel® Xeon® server class processors released 2009 and later.
AMD Opteron™ server class processors released 2010 and later.
Zing is supported on systems with 2 or more vCores. Systems with higher core counts are obviously going to scale better, and provide lower scheduling related hiccup/jitter behavior.
The Zing components in the ZVM with ZST mode, require the following amount of RAM on the ZVM machine:
- 8+ GB RAM recommended
- 512 MB hard minimum
Zing fundamentally leverages any provided memory across a wide operating range. Zing can fit within in the same resource profile as HotSpot, though unlocks a much higher upper memory limit without adversely affecting pause times.
Zing supports heap sizes from 512 MB to 20 TB.
With virtualized environments, we recommend using at least 7.5 GB of physical memory (for example, EC2 xlarge instances) per instance as minimum.
|Cloud Computing Service||Supported Instance||Virtual Processor(s)||RAM|
|Amazon Web Services||t2.medium||2 vCPUs||4 GB or larger|
|Microsoft Azure||Standard_B2s||2 vCPUs||4 GB or larger|
|Google Cloud Platforms||n1-standard-1||1 vCPU||3.75 GB or larger|
One of the benefits of Zing's heap management behavior is that larger Java heaps result in better GC efficiency (often much better than HotSpot), without the typical higher-pause-time downsides often found with other JVMs. As a result, we often recommend systematically starting high, then walking down to determine the proper heap size that provides sufficient headroom to allow improved CPU efficiency for Java applications.
Zing supports heap sizes from 512 MB to 20 TB when used with ZST. When used without ZST, the supported heap size ranges from 512 MB to 2.5 TB.
The Pool license server requires the following amount of RAM on the license server machine.
- 8 GB RAM recommended (4 GB minimum)
Hard Disk Storage Space Requirements
The Zing components require the following amount of disk space on the ZVM machine.
- 10 GB free disk drive space recommended for your ZVM instances to run Java applications
- 8 GB minimum configuration is a spinning platter hard drive or enterprise quality SSD. Installation to a USB flash device is not recommended for production use.
- 600 MB additional for JDK functions
The Pool license server requires the following amount of disk space on the license server machine.
- 10 GB free disk space recommended (5 GB minimum)
Zing with the ZST runs on any of the following hardware or virtualized platforms:
x86-64 virtual machines configured with Intel VT-x or AMD-V (e.g., Amazon EC2 (HVM), Azure, Oracle Virtual Box, Google Compute Engine, VMware)
- Zing System Tools Release Notes
- ZVM with ZST Installation Prerequisites Details
- Installing the Zing System Tools
- Installing the Zing Virtual Machine with ZST
- Installing Zing System Tools Using DKMS
- Verifying Zing Virtual Machine with ZST Installation
- Zing Virtual Machine with ZST Post Installation Tasks
- Run a Java Application with ZVM and ZST
- Zing Compatibility Reference
- Zing ZST Compatibility and API Versions
- Transparent HugePages Settings
- ZST Memory Configuration
- Installing and Configuring Zing Using Read-Only Images
- Upgrading or Uninstalling Zing Components
- ZVM with ZST Monitoring and Management
© Azul Systems, Inc. 2020 All rights reserved.