You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2017/04/17 23:53:41 UTC
[jira] [Assigned] (IGNITE-4961) Document Page Memory API,
Architecture and Behavior
[ https://issues.apache.org/jira/browse/IGNITE-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Magda reassigned IGNITE-4961:
-----------------------------------
Assignee: Alexey Goncharuk (was: Denis Magda)
> Document Page Memory API, Architecture and Behavior
> ---------------------------------------------------
>
> Key: IGNITE-4961
> URL: https://issues.apache.org/jira/browse/IGNITE-4961
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Denis Magda
> Assignee: Alexey Goncharuk
> Priority: Blocker
> Fix For: 2.0
>
>
> The goal of this ticket is to provide extensive documentation around the new page memory architecture introduced in Apache Ignite 2.0.
> Refer to IGNITE-3477 and do the following as a part of this ticket:
> * page memory architecture, advantages, and usage.
> * page memory policies (IGNITE-4960).
> * rework or discontinue Off-Heap Memory page (https://apacheignite.readme.io/docs/off-heap-memory) that lists all the memory tiers supported in versions 1.x. For instance, the swap space is no longer available (IGNITE-4736) and the Java heap is no more a default one and used just as a cache of the page memory (IGNITE-4535).
> Once the Java documentation is ready, assign the ticket to [~ptupitsyn] and [~isapego] who will create .NET and C++ counterparts following a Java template.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)