ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denis Magda (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4961) Document Page Memory API, Architecture and Behavior
Date Thu, 20 Apr 2017 17:43:04 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977129#comment-15977129
] 

Denis Magda commented on IGNITE-4961:
-------------------------------------

In addition, the doc has to mention the last minute changes that will make the memory expandable:
https://issues.apache.org/jira/browse/IGNITE-5024

> 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
>          Components: documentation
>            Reporter: Denis Magda
>            Assignee: Prachi Garg
>            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)

Mime
View raw message