You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ignite.apache.org by ds...@apache.org on 2017/10/12 21:48:27 UTC
svn commit: r1812054 - /ignite/site/trunk/whatisignite.html
Author: dsetrakyan
Date: Thu Oct 12 21:48:26 2017
New Revision: 1812054
URL: http://svn.apache.org/viewvc?rev=1812054&view=rev
Log:
Minor.
Modified:
ignite/site/trunk/whatisignite.html
Modified: ignite/site/trunk/whatisignite.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1812054&r1=1812053&r2=1812054&view=diff
==============================================================================
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Thu Oct 12 21:48:26 2017
@@ -78,12 +78,8 @@ under the License.
</p>
<h3>Ignite Persistence</h3>
<p>
- Ignite <a href="/features/persistence.html">native persistence</a> is a distributed, ACID, and SQL-compliant <i><strong>disk store</strong></i> that transparently integrates with Ignite's Durable Memory as an
- optional disk layer storing data and indexes on SSD, Flash, 3D XPoint, and other types of non-volatile storages.
-
- With the Ignite persistence enabled, you no longer need to keep all the data and indexes in memory or warm it up after a node or
- cluster restart because the Durable Memory is tightly coupled with persistence and treats it as a secondary memory tier.
- This implies that if a subset of data or an index is missing in RAM, the Durable Memory will take it from the disk.
+ Ignite <a href="/features/persistence.html">native persistence</a> is a distributed,
+ strongly consistent <i><strong>disk store</strong></i> that transparently integrates with Ignite's <i>durable memory</i>.
</p>
<h3>ACID Compliance</h3>
<p>