Return-Path:
- Ignite supports 2 modes for caching data in-memory:
-
- Whenever off-heap memory is configured, Ignite will also store query indexes off-heap
- as well. This means that indexes will not take any portion of on-heap memory.
-
- As data gets colder (not accessed) Ignite will optionally migrate it
- from On-Heap memory to Off-Heap memory, and from Off-Heap memory to Swap (disk) storage.
-
- Whenever some data is accessed, it will immediately be propagated to the top tier
- pushing some other colder data down the next memory tier.
+ Apache Ignite
- Starting from v1.5 Ignite introduced a new concept of storing data in caches, called BinaryObjects. It allows you to:
+ Apache Ignite stores data in caches as
-
- Off-Heap and On-Heap Memory
+ Page Memory
- off-heap
and
- on-heap
.
- Off-Heap memory allows your cache to overcome lengthy JVM Garbage Collection (GC) pauses
- when working with large heap sizes by caching data outside of main Java Heap space,
- but still in RAM.
-
-
- Off-Heap Indexes
-
-
-
-
@@ -458,7 +425,7 @@ under the License.
Ignite allows developers to define explicit locks enforcing mutual exclusion on cached objects.
Tiered Storage
-
- Page Memory
is a manageable off-heap based memory architecture that is split into pages of fixed size. Ignite stores data in off-heap memory with an option to store data on-heap.
Binary Protocol
BinaryObjects
that allows you to: