lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Littlestar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-5928) WildcardQuery may has memory leak
Date Tue, 09 Sep 2014 09:48:29 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126800#comment-14126800
] 

Littlestar commented on LUCENE-5928:
------------------------------------

when I changed to NIO, It works OK.
Does MMAP use a lot of NativeMemory?

> WildcardQuery may has memory leak
> ---------------------------------
>
>                 Key: LUCENE-5928
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5928
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/search
>    Affects Versions: 4.9
>         Environment: SSD 1.5T, RAM 256G 10*10000
>            Reporter: Littlestar
>
> data 800G, records 15*10000*10000.
> one search thread.
> content:???
> content:*
> content:*1
> content:*2
> content:*3
> jvm heap=96G, but the jvm memusage over 130g?
> run more wildcard, use memory more....
> Does luence search/index use a lot of DirectMemory or Native Memory?
> I use -XX:MaxDirectMemorySize=4g, it does nothing better.
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message