ignite-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dma...@apache.org
Subject svn commit: r1833364 - in /ignite/site/trunk/arch: durablememory.html memorycentric.html
Date Mon, 11 Jun 2018 23:01:57 GMT
Author: dmagda
Date: Mon Jun 11 23:01:57 2018
New Revision: 1833364

URL: http://svn.apache.org/viewvc?rev=1833364&view=rev
Log:
Added durable memory modes

Modified:
    ignite/site/trunk/arch/durablememory.html
    ignite/site/trunk/arch/memorycentric.html

Modified: ignite/site/trunk/arch/durablememory.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/arch/durablememory.html?rev=1833364&r1=1833363&r2=1833364&view=diff
==============================================================================
--- ignite/site/trunk/arch/durablememory.html (original)
+++ ignite/site/trunk/arch/durablememory.html Mon Jun 11 23:01:57 2018
@@ -77,7 +77,75 @@ under the License.
                 indexes on disk (assuming that Ignite Native Persistence is enabled), while
Virtual Memory uses the
                 disk when it runs out of RAM, for swapping purposes only.
             </p>
-            <h2 style="padding-top: 10px;">Ignite Native Persistence</h2>
+
+            <div class="page-heading">Durable Memory Modes</div>
+            <table class="formatted" name="Deployment Options Features">
+                <thead>
+                <tr>
+                    <th width="35%" class="left">Mode</th>
+                    <th>Description</th>
+                </tr>
+                </thead>
+                <tbody>
+                <tr>
+                    <td class="left">In-Memory</td>
+                    <td>
+                        <p>
+                            The whole data set is stored in memory. In this scenario, you
can achieve the maximum
+                            performance possible because the data is never written to disk.
To prevent possible data
+                            loss when a single cluster node fails, it is recommended to configure
a number of backup
+                            copies (aka. replication factor) appropriately.
+                            <a href="/arch/durablememory.html#swap-space">Swap space</a>
can be used to prevent memory
+                            overflow.
+                        </p>
+
+                        <p>
+                            <strong>Use cases</strong>: in-memory computations,
+                            <a href="/use-cases/caching/web-session-clustering.html">Web-session
clustering</a>,
+                            state caching, real-time processing of never-ending streams of
data.
+                        </p>
+                    </td>
+                </tr>
+                <tr>
+                    <td class="left">In-Memory + Full Copy on Disk</td>
+                    <td>
+                        <p>
+                            The whole data set is stored both in memory and on disk. The
disk is used for recovery
+                            purpose. <a href="/arch/durablememory.html#native-persistence">Ignite
persistence</a>
+                            or a <a href="/arch/durablememory.html#3rd-party-persistence">3rd
party database</a>
+                            can be used as a persistence layer.
+                        </p>
+
+                        <p>
+                            <strong>Use cases</strong>: Ignite as an
+                            <a href="/features/datagrid.html"><nobr>In-Memory
Data Grid</nobr></a> or
+                            <a href="/use-cases/caching/database-caching.html">distributed
cache</a>
+                            which scales out and accelerates existing RDBMS and NoSQL deployments.
+                        </p>
+                    </td>
+                </tr>
+                <tr>
+                    <td class="left">100% on Disk + X% in Memory</td>
+                    <td>
+                        <p>
+                            100% of data is stored in <a href="/arch/durablememory.html#native-persistence">Ignite
persistence</a>
+                            and X% of data is cached in memory. X is solely defined by your
hardware resources. The
+                            more data is cached the faster is the performance. The disk becomes
your primary storage.
+                        </p>
+
+                        <p>
+                            <strong>Use cases</strong>: Ignite as a memory-centric
+                            <a href="/use-cases/database/distributed-database.html"><nobr>distributed
database</nobr></a>.
+                        </p>
+                    </td>
+                </tr>
+                </tbody>
+            </table>
+
+            <h2 style="padding-top: 10px;" id="native-persistence">
+                Ignite Native Persistence
+                <a href="/arch/durablememory.html#native-persistence"><i class="fa
fa-anchor"></i></a>
+            </h2>
             <p>
                 Ignite Persistence is the most flexible, scalable, and convenient way of
persisting data in Ignite.
                 It is widely used in scenarios where applications need a distributed memory-centric
database
@@ -115,7 +183,10 @@ under the License.
                 </ul>
             </div>
 
-            <h2 style="padding-top: 10px;">3rd Party Persistence</h2>
+            <h2 style="padding-top: 10px;" id="3rd-party-persistence">
+                3rd Party Persistence
+                <a href="/arch/durablememory.html#3rd-party-persistence"><i class="fa
fa-anchor"></i></a>
+            </h2>
             <p>
                 Ignite can be used as a caching layer (aka. data grid) above an existing
3rd party
                 database - RDBMS, NoSQL, or HDFS. This mode is used to accelerate the underlying
database that persists
@@ -126,7 +197,10 @@ under the License.
                 to memory beforehand.
             </p>
 
-            <h2 style="padding-top: 10px;">Swap Space</h2>
+            <h2 style="padding-top: 10px;" id="swap-space">
+                Swap Space
+                <a href="/arch/durablememory.html#swap-space"><i class="fa fa-anchor"></i></a>
+            </h2>
             <p>
                 If you do not want to use Ignite native persistence or 3rd party persistence,
you can enable swapping,
                 in which case, Ignite in-memory data will be moved to the swap space located
on disk if you run out of RAM.

Modified: ignite/site/trunk/arch/memorycentric.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/arch/memorycentric.html?rev=1833364&r1=1833363&r2=1833364&view=diff
==============================================================================
--- ignite/site/trunk/arch/memorycentric.html (original)
+++ ignite/site/trunk/arch/memorycentric.html Mon Jun 11 23:01:57 2018
@@ -77,6 +77,11 @@ under the License.
                 difference here from the traditional disk-centric RDBMS or NoSQL system is
that Ignite is strongly consistent,
                 horizontally scalable, and supports both SQL and key-value processing APIs.
             </p>
+            <p>
+                Read more about Ignite's <i>durable memory</i> and its operational
modes
+                <a href="/arch/durablememory.html">here</a>.
+            </p>
+
 
             <div class="page-heading">Collocated vs Client-Server Processing</div>
             <p>
@@ -110,37 +115,6 @@ under the License.
                 all cluster members.
             </p>
 
-            <div class="page-heading">Ignite as In-Memory Store</div>
-            <p>
-                The persistence is totally optional in Ignite that allows using the cluster
in the memory-only mode
-                where all the data and indexes are stored solely in RAM. In this scenario,
you can achieve the maximum
-                performance possible because the data is never written to disk. To prevent
possible data loss when a
-                single cluster node fails, it is recommended to configure a number of backup
copies (aka. replication
-                factor) appropriately.
-            </p>
-
-            <div class="page-heading">Ignite Persistence</div>
-            <p>
-                There are two ways to enable persistence in Ignite. The first approach is
to use its own distributed,
-                ACID, and <nobr>SQL-compliant</nobr> persistence that transparently
and efficiently integrates with
-                overall memory architecture.
-            </p>
-            <p>
-                With the the native persistence enabled, Ignite always stores a superset
of data on disk,
-                and as much as possible in RAM. For example, if there are
-                100 entries and RAM has the capacity to store only 20, then all 100 will
be stored on disk
-                and only 20 will be cached in RAM for better performance.
-            </p>
-
-            <div class="page-heading">Ignite and 3rd Party Database</div>
-            <p>
-                The second approach to have the persistence enabled, is to deploy Ignite
above an existing 3rd party database
-                such as RDBMS, Apache Cassandra or MongoDB. This mode is usually used to
accelerate the underlying
-                database by storing a copy of the data in memory in Ignite. Ignite supports
both read-through and
-                write-through modes that ensure data consistency and keeps Ignite and the
database in sync. Refer to
-                <a href="/arch/persistence.html" target="doc">Ignite persistence</a>
page to compare Ignite persistence
-                vs 3rd Party Persistence modes.
-            </p>
 
             <div class="page-heading">More on Memory-Centric Storage</div>
             <table class="formatted" name="Deployment Options Features">



Mime
View raw message