ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Schmitt <peter.schmitt....@gmail.com>
Subject Re: OFFHEAP_TIERED and memory fragmentation
Date Wed, 25 Jan 2017 09:32:50 GMT
Hi Val,

fair enough :-)
However, in the source-code it looks like "Flexible and precise per-cache
memory limit" is supported already.
At least each GridUnsafeMemory instance (in each GridCacheContext) receives
the value from CacheConfiguration.getOffHeapMaxMemory).
I haven't debugged it, but the instances are created per cache.

Furthermore, I'm not sure about the memory-page concept, because you would
get pages on top of pages (used by a modern OS).
Sounds like even more fragmentation and in this case Ignite would need to
do the defragmentation.

Kind regards,
Peter



2017-01-25 1:56 GMT+01:00 vkulichenko <valentin.kulichenko@gmail.com>:

> I don't think I will be able to explain better than it's done in the ticket
> :) Current approach is naive and not always effective for multiple reasons.
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/OFFHEAP-TIERED-and-memory-fragmentation-tp10218p10235.
> html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Mime
View raw message