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 any other process operates in its virtual memory space and the OS share the physical RAM between all the processes. [1] https://stackoverflow.com/questions/14347206/what-are-the-differences-between-virtual-memory-and-physical-memory On Thu, Aug 2, 2018 at 8:52 AM Dmitriy Govorukhin < [email protected]> wrote: > 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 <[email protected]> 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 post), the memory displayed in PCF server was never decreased, and >> we >> need some way to reduce the memory in used on PCF by 200 MB to avoid a >> lack >> of memory. Thanks again. >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> >
