lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LUCENE-4740) Weak references cause extreme GC churn
Date Thu, 31 Jan 2013 16:29:14 GMT

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

Uwe Schindler edited comment on LUCENE-4740 at 1/31/13 4:28 PM:
----------------------------------------------------------------

bq. I replaced those maps with regular ConcurrentHashMap<Class, X> without any negative
impact.

This kills the possibility of unloading web applications in application servers. Those maps
don't produce many references.

Which OS are you using? Somebody had a similar problem on Windows - but on Linux all was fine.
Maybe some JVM version has a bug in reference queues... Can you give your exact version number?
                
      was (Author: thetaphi):
    bq. I replaced those maps with regular ConcurrentHashMap<Class, X> without any negative
impact.

This kills the possibility of unloading web applications in application servers. Those maps
don't produce many references.

Which OS are you using? Somebody had a similar problem on Windows.
                  
> Weak references cause extreme GC churn
> --------------------------------------
>
>                 Key: LUCENE-4740
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4740
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/store
>    Affects Versions: 3.6.1
>         Environment: Linux debian squeeze 64 bit, Oracle JDK 6, 32 GB RAM, 16 cores
>            Reporter: Kristofer Karlsson
>            Priority: Critical
>
> We are running a set of independent search machines, running our custom software using
lucene as a search library. We recently upgraded from lucene 3.0.3 to 3.6.1 and noticed a
severe degradation of performance.
> After doing some heap dump digging, it turns out the process is stalling because it's
spending so much time in GC. We noticed about 212 million WeakReference, originating from
WeakIdentityMap, originating from MMapIndexInput.
> Our problem completely went away after removing the clones weakhashmap from MMapIndexInput,
and as a side-effect, disabling support for explictly unmapping the mmapped data.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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


Mime
View raw message