[ https://issues.apache.org/jira/browse/LUCENE-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Heisey updated LUCENE-5928: --------------------------------- Attachment: idxb1-top-sorted-mem.png > 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, records 15*10000*10000 > Reporter: Littlestar > Assignee: Uwe Schindler > Attachments: idxb1-top-sorted-mem.png, 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org