Hi,
I believe this is a function of the OS, not the application. In modern OS
implementations (Linux variants, anyway), for performance reasons, once
memory is allocated from the kernel, it is not returned to the kernel until
the process exits.
The performance hit of doing context switching to
Forgot to attach the link for the documentation:
https://ignite.apache.org/docs/latest/installation/kubernetes/gke-deployment
On Fri, Dec 23, 2022 at 1:43 AM Wen Bo (Bill) Li wrote:
> Hi,
>
> I have encountered an issue in deploying Ignite on Kubernetes using the
> deployment object. By
Is there a way I can see how much of that claimed memory of Ignite is
available when caches are cleared? Currently we are in production and there
we see that the memory consumed by our pods are passing above 90%.
But we are clearing caches and filling them with new data to do new
calculations. I
Hi, but Ignite doesn't and never did release memory back to the OS, except
only on deactivation or shutting down.
пт, 23 дек. 2022 г. в 10:46, Humphrey Lopez :
> Hello,
>
> I've been doing some test with Ignite 2.14, creating one cache filling it
> with data and then clearing back the cache,
