lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Littlestar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENE-5928) WildcardQuery may has memory leak
Date Wed, 10 Sep 2014 01:43:28 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Littlestar updated LUCENE-5928:
-------------------------------
    Attachment: top_java.jpg

hi, 
   when using default MMapDirectory,  jvm heap=96G,  the java process RES over 130g, not VIRT(VIRT
>=900G).

see attachement, thanks.


> 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
>            Assignee: Uwe Schindler
>         Attachments: top_java.jpg
>
>
> 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