Val, thanks for pointing this out.

I would actually not allocate any off-heap memory on the client side unless
we see Local caches in the configuration. This is such a rare case, that we
can ignore it altogether.

D.

On Fri, Jul 20, 2018 at 3:59 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Folks,
>
> Currently do not create any regions or allocate any offheap memory on
> client nodes unless it's explicitly configured. This is good behavior,
> however there is a usability issue caused by the fact that many users have
> the same config file for both server and clients. This can lead to
> unexpected excessive memory usage on client side and forces users to
> maintain two config files in most cases.
>
> At the same time, the only case when offheap memory can be required on a
> client node is using LOCAL caches there, which is a very rare use case.
>
> Having said that, is it possible to allocate memory on client node
> dynamically ONLY if a local cache is created there? This would fix the
> usability issue without limiting the use of local caches on client side.
>
> -Val
>

Reply via email to