This is an automated email from the ASF dual-hosted git repository.
dmagda pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ignite.git
The following commit(s) were added to refs/heads/master by this push:
new 8ff5158 IGNITE-14932 Reference to the Ignite Storage Overview video
(#9181)
8ff5158 is described below
commit 8ff515843d155288a8ce29cb240ef2c20e987c2d
Author: Nikita Safonov <73828260+nikita-tech-wri...@users.noreply.github.com>
AuthorDate: Thu Jun 17 20:49:32 2021 +0300
IGNITE-14932 Reference to the Ignite Storage Overview video (#9181)
* IGNITE-14932 Reference to the Ignite Storage Overview video
* Minor fix
---
docs/_docs/persistence/native-persistence.adoc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/docs/_docs/persistence/native-persistence.adoc
b/docs/_docs/persistence/native-persistence.adoc
index ee8e652..14e9e6a 100644
--- a/docs/_docs/persistence/native-persistence.adoc
+++ b/docs/_docs/persistence/native-persistence.adoc
@@ -22,6 +22,8 @@ Ignite Persistence, or Native Persistence, is a set of
features designed to prov
When it is enabled, Ignite always stores all the data on disk, and loads as
much data as it can into RAM for processing.
For example, if there are 100 entries and RAM has the capacity to store only
20, then all 100 are stored on disk and only 20 are cached in RAM for better
performance.
+NOTE: For more information on Native Persistence, watch
link:https://www.youtube.com/watch?v=6Yg5QW-XFVc&list=PLMc7NR20hA-KF8c_hVICKpzKnWkjzfC2V&index=19[the
architectural deep dive, window=_blank] on the internals of the Ignite storage
engine.
+
When Native persistence is turned off and no external storage is used, Ignite
behaves as a pure in-memory store.
When persistence is enabled, every server node persists a subset of the data
that only includes the partitions that are assigned to that node (including
link:data-modeling/data-partitioning#backup-partitions[backup partitions] if
backups are enabled).
