Prasad,
Thank you for sharing results!
пн, 18 февр. 2019 г. в 20:06, Prasad Bhalerao :
>
> Hi,
>
> Thank you for the hint. I just wrote a small program to allocate 1 GB memory
> and to free the same memory using UNSAFE api. I took the native memory
> tracking report 3 times, before allocating 1
Hi,
Thank you for the hint. I just wrote a small program to allocate 1 GB
memory and to free the same memory using UNSAFE api. I took the native
memory tracking report 3 times, before allocating 1 GB memory, after
allocating 1 GB memory and after freeing 1 GB memory.
Here is the snippet of report
Prasad,
Someone has already posted a snippet [1].
[1] https://gist.github.com/prasanthj/48e7063cac88eb396bc9961fb3149b58
пн, 18 февр. 2019 г. в 17:23, Павлухин Иван :
>
> Hi Prasad,
>
> As far as I remember offheap memory allocated with use of Unsafe is
> not reflected in Native Memory Tracking
Hi Prasad,
As far as I remember offheap memory allocated with use of Unsafe is
not reflected in Native Memory Tracking report. You are right that
documentation is not verbose about reported categories [1]. It might
be the case that memory allocated by ByteBuffer.allocateDirect falls
into "internal
Hi.
Please don't use posting to both dev/user lists simultaneously.
If your question is not related to any contribution you are planning to do,
then the user list is a better place to ask, because a possible answer may
be interesting to all Ignite users.
If you are going to fix any issue and wou
Hi,
I have set the off heap size to 500 MB and max heap size to 512 MB.
My process is taking around 1.7 GB on Windows 10 as per the task manager.
So I decided to track the memory distribution using jcmd to find out if
there are any memory leaks in non-heap space.
After pushing the data to cache
