High performance native memory access for Java.

Clone this repo:
  1. cd82c73 Release Process: Change pom version to 2.3.0-SNAPSHOT. by David Cromberge · 4 weeks ago master 2.3.0-SNAPSHOT
  2. f2545b1 Merge pull request #166 from apache/fix-coverage-report by Lee Rhodes · 4 weeks ago
  3. 036da58 Fix jacoco plugin report by David Cromberge · 4 weeks ago
  4. 6577d85 Merge pull request #165 from apache/fix-eclipse-warning by Lee Rhodes · 4 weeks ago
  5. ba4a144 Remove redundant version declaration by David Cromberge · 4 weeks ago

Build Status Maven Central Language grade: Java Total alerts Coverage Status

=================

DataSketches Java Memory Component

This Memory component is general purpose, has no external runtime dependencies and can be used in any application that needs to manage data structures inside or outside the Java heap.

The goal of this component of the DataSketches library is to provide a high performance access API for accessing four different types of memory resources. Each of the four resource types is accessed using different API methods in the Memory component.

  • Heap: Contiguous bytes on the Java Heap constructed by, e.g., WritableMemory.writableWrap(byte[]) or using the WritableMemory.allocate(int) method. For purposes of this document this includes on-heap ByteBuffers constructed using ByteBuffer.allocate(int).

  • DirectByteBuffer: Contiguous bytes of a ByteBuffer constructed by, e.g., WritableMemory.writableWrap(ByteBuffer) where the ByteBuffer was previously constructed using ByteBuffer.allocateDirect(int); or, is a slice() thereof.

  • Direct: Contiguous bytes off the Java Heap constructed by, e.g., WritableMemory.allocateDirect(long) method.

  • Memory-Mapped Files Contiguous bytes of a file represented in off-heap memory and created using, e.g., the WritableMemory.writableMap(File) method.

Please visit the main DataSketches website for more information.

If you are interested in making contributions to this Memory component please see our Community page.

Release 2.0.0+

Starting with release datasketches-memory-2.0.0, this Memory component supports Java 8 through Java 13. Providing access to the four contiguous byte resources (mentioned above) in Java 8 only requires reflection. However, Java 9 introduced the Java Platform Module System (JPMS) where access to these internal classes requires starting up the JVM with special JPMS arguments. The actual JVM arguments required will depend on how the user intends to use the Memory API, the Java version used to run the user‘s application and whether the user’s application is a JPMS application or not.

Also see the usage examples for more information.

USE AS A LIBRARY (using jars from Maven Central)

In this environment, the user is using the Jars from Maven Central as a library dependency and not attempting to build the Memory component from the source code or run the Memory component tests.

  • If you are running Java 8, no extra JVM arguments are required.
  • If you are running Java 11-13 and only using the Heap related API, no extra JVM arguments are required.

Otherwise, if you are running Java 11-13 and ...

  • If your application is not a JPMS module use the following table. Choose the columns that describe your use of the Memory API. If any of the columns contain a Yes, then the JVM argument in the first column of the row containing a Yes will be required. If you are not sure the extent of the Memory API being used, there is no harm in specifying all 4 JVM arguments. Note: do not embed any spaces in the full argument.
JVM Arguments for non-JPMS ApplicationsDirect ByteBufferDirectMemoryMapped Files
--add-exports java.base/jdk.internal.misc= ALL-UNNAMEDYes
--add-exports java.base/jdk.internal.ref= ALL-UNNAMEDYesYes
--add-opens java.base/java.nio= ALL-UNNAMEDYesYes
--add-opens java.base/sun.nio.ch= ALL-UNNAMEDYes
  • If your application is a JPMS module use the following table. Choose the columns that describe your use of the Memory API. If any of the columns contain a Yes, then the JVM argument in the first column of the row containing a Yes will be required. If you are not sure the extent of the Memory API being used, there is no harm in specifying all 4 JVM arguments. Note: do not embed any spaces in the full argument.
JVM Arguments for JPMS ApplicationsDirect ByteBufferDirectMemoryMapped Files
--add-exports java.base/jdk.internal.misc= org.apache.datasketches.memoryYes
--add-exports java.base/jdk.internal.ref= org.apache.datasketches.memoryYesYes
--add-opens java.base/java.nio= org.apache.datasketches.memoryYesYes
--add-opens java.base/sun.nio.ch= org.apache.datasketches.memoryYesYes

DEVELOPER USAGE

In this environment the developer needs to build the Memory component from source and run the Memory Component tests. There are two use cases. The first is for a System Developer that needs to build and test their own Jar from source for a specific Java version. The second use case is for a Memory Component Developer and Contributor.

  • System Developer

    • Compile, test and create a Jar for a specific Java version
      • use the provided script for this purpose
  • Memory Component Developer / Contributor

    • Compile & test the library from source code using:
      • Eclipse (version)
      • IntelliJ (version)
      • Maven (version)
      • Command-line or scripts
    • The developer must have installed in their development system at least JDK versions 8 and 11.
    • Unless building with the provided script, the developer must have a valid Maven toolchain configuration.

Build Instructions

NOTES:

  1. This component accesses resource files for testing. As a result, the directory elements of the full absolute path of the target installation directory must qualify as Java identifiers. In other words, the directory elements must not have any space characters (or non-Java identifier characters) in any of the path elements. This is required by the Oracle Java Specification in order to ensure location-independent access to resources: See Oracle Location-Independent Access to Resources

Dependencies

There are no run-time dependencies. See the pom.xml file for test dependencies.

Maven build instructions

The Maven build requires the following JDKs to compile:

  • JDK8/Hotspot
  • JDK11/Hotspot

Before building, first ensure that your local environment has been configured according to the Maven Toolchains Configuration.

There are three types of tests: normal unit tests, tests run by the strict profile and continuous integration(CI) tests. The CI tests target the Multi-Release (MR) JAR and run the entire test suite using a specific version of Java. Running the CI test command also runs the default unit tests.

To run normal unit tests:

mvn clean test

To run the strict profile tests (only supported in Java 8):

mvn clean test -P strict

To run javadoc on this multi-module project, use:

mvn clean javadoc:javadoc -DskipTests=true

To build the multi-release JAR, use:

mvn clean package

To run the eclipse plugin on this multi-module project, use:

mvn clean eclipse:eclipse -DskipTests=true

To install jars built from the downloaded source:

mvn clean install -DskipTests=true

This will create the following Jars:

  • datasketches-memory-X.Y.Z.jar The compiled main class files.
  • datasketches-memory-X.Y.Z-tests.jar The compiled test class files.
  • datasketches-memory-X.Y.Z-sources.jar The main source files.
  • datasketches-memory-X.Y.Z-test-sources.jar The test source files
  • datasketches-memory-X.Y.Z-javadoc.jar The compressed Javadocs.

Building for a specific java version

A build script named compile-package-jar.sh has been provided to package a JAR for a specific java version. This is necessary in cases where a developer is unable to install all the required versions of the JDK that are required as part of the Maven build.

The build script performs the following steps:

  1. Sets up staging directories under target/ for the package files
  2. Uses git commands to gather information about the current Git commit and branch
  3. Compiles java source tree
  4. Packages a JAR containing compiled sources together with the Manifest, Licence and Notice files
  5. Checks and tests the assembled JAR by using the API to access four different resource types

The build script is located in the tools/scripts/ directory and requires the following arguments:

  • JDK Home Directory - The first argument is the absolute path of JDK home directory e.g. $JAVA_HOME
  • Git Version Tag - The second argument is the Git Version Tag for this deployment e.g. 1.0.0-SNAPSHOT, 1.0.0-RC1, 1.0.0 etc.
  • Project Directory - The third argument is the absolute path of project.basedir e.g. /src/apache-datasketches-memory

For example, if the project base directory is /src/datasketches-memory;

To run the script for a release version:

./tools/scripts/compile-package-jar.sh $JAVA_HOME 2.1.0 /src/datasketches-memory

To run the script for a snapshot version:

./tools/scripts/compile-package-jar.sh $JAVA_HOME 2.2.0-SNAPSHOT /src/datasketches-memory

To run the script for an RC version:

./tools/scripts/compile-package-jar.sh $JAVA_HOME 2.1.0-RC1 /src/datasketches-memory

Note that the script does not use the Git Version Tag to adjust the working copy to a remote tag - it is expected that the user has a pristine copy of the desired branch/tag available before using the script.


Further documentation for contributors

For more information on the project configuration, the following topics are discussed in more detail:

In order to build and contribute to this project, please read the relevant IDE documentation: