You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Shawn Du <sh...@neulion.com.cn> on 2016/10/28 04:08:05 UTC
Memeory Leaks of Swapspace
Hi devs.
I am running ignite github master branch.
My case is simple, use OFF_HEAP and enable swap. For I know this bug
(https://issues.apache.org/jira/browse/IGNITE-3840) isn't merge into the
master.
So I disable any expiry policy.
After running for a while, I checked the memory usage of ignite. I can see
Java heap memory keep growing.
I dump the heap and using MAT to analyze and found:
Most memory ase used by org.apache.ignite.spi.swapspace.SwapKey.
It is a bug or designed purposely? I need a stable version of no memory
issue, I tried 1.7.0, 1.8.0 master and some pull request version, but none
of them work.
Please help.
Thanks
Re: 答复: Memeory Leaks of Swapspace
Posted by Valentin Kulichenko <va...@gmail.com>.
What is the reason for using swap space in the first place? In most cases
there is a way to avoid this and you should do this whenever possible.
P.S. Such questions are actually for user list, not for dev list. Please
post them there going there.
-Val
On Thu, Oct 27, 2016 at 10:59 PM, Shawn Du <sh...@neulion.com.cn> wrote:
> Just go through the code and find this:
>
>
>
> * File-based swap space SPI implementation which holds keys in memory. This
> SPI is used by default.
> * It is intended for use in cases when value size is bigger than {@code
> 100}
> bytes, otherwise it will not
> * have any positive effect.
>
>
>
> So it is designed purposely. My cache entries are small, so …
>
>
>
> Any plan to use Rockdb to implement the swap spi interface?
>
>
>
> Thanks.
>
>
>
> 发件人: Shawn Du [mailto:shawn.du@neulion.com.cn]
> 发送时间: 2016年10月28日 12:08
> 收件人: dev@ignite.apache.org
> 主题: Memeory Leaks of Swapspace
>
>
>
> Hi devs.
>
>
>
> I am running ignite github master branch.
>
> My case is simple, use OFF_HEAP and enable swap. For I know this bug
> (https://issues.apache.org/jira/browse/IGNITE-3840) isn’t merge into the
> master.
>
> So I disable any expiry policy.
>
> After running for a while, I checked the memory usage of ignite. I can see
> Java heap memory keep growing.
>
> I dump the heap and using MAT to analyze and found:
>
> Most memory ase used by org.apache.ignite.spi.swapspace.SwapKey.
>
>
>
> It is a bug or designed purposely? I need a stable version of no memory
> issue, I tried 1.7.0, 1.8.0 master and some pull request version, but none
> of them work.
>
>
>
> Please help.
>
>
>
> Thanks
>
>
答复: Memeory Leaks of Swapspace
Posted by Shawn Du <sh...@neulion.com.cn>.
Just go through the code and find this:
* File-based swap space SPI implementation which holds keys in memory. This
SPI is used by default.
* It is intended for use in cases when value size is bigger than {@code 100}
bytes, otherwise it will not
* have any positive effect.
So it is designed purposely. My cache entries are small, so …
Any plan to use Rockdb to implement the swap spi interface?
Thanks.
发件人: Shawn Du [mailto:shawn.du@neulion.com.cn]
发送时间: 2016年10月28日 12:08
收件人: dev@ignite.apache.org
主题: Memeory Leaks of Swapspace
Hi devs.
I am running ignite github master branch.
My case is simple, use OFF_HEAP and enable swap. For I know this bug
(https://issues.apache.org/jira/browse/IGNITE-3840) isn’t merge into the
master.
So I disable any expiry policy.
After running for a while, I checked the memory usage of ignite. I can see
Java heap memory keep growing.
I dump the heap and using MAT to analyze and found:
Most memory ase used by org.apache.ignite.spi.swapspace.SwapKey.
It is a bug or designed purposely? I need a stable version of no memory
issue, I tried 1.7.0, 1.8.0 master and some pull request version, but none
of them work.
Please help.
Thanks