ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Page Memory behavior with default memory policy
Date Tue, 18 Apr 2017 01:05:56 GMT
On Mon, Apr 17, 2017 at 6:00 PM, Denis Magda <dmagda@apache.org> wrote:

> Dmitriy,
> All the nodes will request its own continuous memory region that takes
> 70-80% of all RAM from an underlying operation system. However, the
> operating system will not outfit the nodes with physical pages mapped to
> RAM immediately allowing every node's process to start successfully. The
> nodes will communicate to RAM via a virtual memory which in its turn will
> give an access to physical pages whenever is needed applying low level
> eviction and swapping techniques.

Denis, it sounds like with this approach, in case of the over-allocation,
the system will just get slower and slower and users will end up blaming
Ignite for it. Am I understanding your suggestion correctly?

How was this handled in Ignite 1.9?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message