This page describes an older version of the product. The latest stable version is 16.2.1.

What's New

This section describes product changes, along with new features and functionality for InsightEdge platform release 12.3.

Tiered Storage (MemoryXtend)

User-Controlled Cache

The LRU on-heap cache has been enhanced to accept user-defined criteria, so that customers can prioritize data availability. Users can create sets of queries that define what data should be cached as hot data in the in-memory data grid, while cold data continues to be stored on disk (SSD or HDD). This is an evolution of an existing API that controlled what data should be cached during initial load; this policy now applies for the entire application lifetime of the data grid.

For more information, see User-Defined Cache.

Off-Heap Storage Driver

In addition to the existing SSD/Disk storage driver, a new storage driver is now available for Off-Heap RAM. This drivers enables users to store data on RAM outside the JVM heap, which is faster than disk access and consumes less memory than on-heap data objects.

For more information, see MemoryXtend for Off-Heap RAM.

Off-Heap Caching for SSD Storage Driver

In systems with MemoryXtend, the InsightEdge platform can store the values of indexed fields in off-heap memory, to avoid having to fetch data from disk (SSD or HDD) for queries that only need the index. This feature can optimize performance by up to 50% for the following operations:

  • Read with projection and only indexed fields in query and projection - primary instance optimization
  • Take with only indexed fields in query - backup optimization
  • Clear with only indexed fields in query - primary and backup instance optimization

For more information, see Off-Heap Cache.

New Command Line Interface

A new Command Line Interface (CLI) is now available, which supports both InsightEdge and XAP applications. The new CLI unifies the user experience across InsightEdge and XAP, and is based on the recent addition of the REST Manager API, enabling users to manage remote or cloud-based environments as easily as managing local machines. In addition, the new CLI provides modern syntax and a user-friendly command structure, along with help screens to guide users in learning how to use the tool.

To get started with the new CLI, simply navigate to the bin folder and run insightedge --help or xap --help (according to the GigaSpaces product being used).

The following is a partial list of the available functionality:

  • Start and stop a Grid Servie Agent (gs-agent) on the current host
  • Deploy and manage a Processing Unit or Space
  • List, create, kill, and restart containers (GSCs)
  • List hosts
  • List Spaces and Space instances
  • Autocomplete of commands

The previous GigaSpaces CLI is still provided and supported, but will be removed in future versions. We encourage users to try the new CLI, and welcome feedback and requests for improvements.

For more information, see Command Line Interface.

Docker Support

Starting with this version, official Docker images for InsightEdge and XAP are provided for both open source and Enterprise editions. The Docker images are available at Docker Hub, and the corresponding Docker files are available on GitHub.

The Docker images leverage the new Command Line Interface and REST Manager API, which provides a seamless experience whether you work with Docker on your local machine, within your enterprise network, or in the cloud.

For more information, see the GigaSpaces Docker Hub Repo.

Memory Footprint

New index types have been introduced, to offer users additional indexing options that require a smaller memory footprint. The new index types are:

  • EQUAL - Performs matching by equality, and should be used instead of the BASIC indexing option.
  • ORDERED - Performs ordered matching.
  • EQUAL_AND_ORDERED - Performs both matching by equality and ordered matching, and should be used instead of the EXTENDED indexing option.

The new ORDERED index consumes less memory than EQUAL_AND_ORDERED, at the cost of matching equality less efficiently. When optimizing for ordered queries alone, this is the preferred index type. When optimizing for both ordered and equality queries, there is a performance-vs-footprint trade-off between ORDERED and EQUAL_AND_ORDERED, which you should consider according to your use case.

For more information, see Index Types.

Third-Party Product Changes

End-Of-Life and Deprecated Features and Functionality

The following functionality is deprecated as of this release:

  • V1 of the REST Manager API (use the new V2 instead)
  • BASIC and EXTENDED index types (use EQUAL | ORDERED | EQUAL_AND_ORDERED instead)

In addition, please note the following:

  • Java 7 is no longer supported. Java 8 is now the minimum supported version.
  • The XAP.NET 32-bit package is end of life as of this release.