I don't see any issue here. The Ignite process shows max virtual memory
size [1] allocated by your operating system (OS) for it during the peak
usage. The data region just grew to that size, and once you remove all the
data, it will be empty (just call cache.size() to confirm this).
So, Ignite as
In the current implementation, Ignite does not support deallocate memory.
Maybe you can try to use ignite with persistence and reduce in-memory
region size?
Please explain your use case in more details and provide Ignite and cache
configurations.
On Mon, Jul 30, 2018 at 8:29 PM okiesong wrote:
>
Hi, first of all, thank you very much for your quick response!
My case is that on the PCF server, once I execute the ignite against the 1.0
million records, my memory usage displayed by the PCF server increase by
200MB. After I execute the destroy cache function (just like I posted in my
above pos
Ignite does not deallocate memory in a region after all caches are stopped.
It is the default behavior.
In future, you may create new caches in this regions without
necessary allocate memory.
Could you please explain your case in more details?
On Fri, Jul 27, 2018 at 4:10 PM okiesong wrote:
> Hi
Hi my ignite version is 2.6. And yes, I am using in-memory options. thanks in
advance!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Do you use the in-memory region for these caches or region with persistence?
What is your ignite version?
On Fri, Jul 27, 2018 at 12:17 AM okiesong wrote:
> Hi, this is basically the command that I am using to clear and destroy the
> cache from the server that is deployed on the PCF server.
Hi, this is basically the command that I am using to clear and destroy the
cache from the server that is deployed on the PCF server.
But memory does not free, even after I do this.
private clearCacheByName(String item) {
if (ignite.cacheNames().contains(item)) {
