JRuby (please use github issues at http://bugs.jruby.org)
  1. JRuby (please use github issues at http://bugs.jruby.org)
  2. JRUBY-1955

Lucene index search causes major memory bloat + slowdown in 1.1RC1, but not 1.1b1

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: JRuby 1.1RC1
    • Fix Version/s: JRuby 1.1RC2
    • Component/s: Java Integration
    • Labels:
      None
    • Environment:
      Mac OS X 10.5.1, Java 1.5.0_13, Lucene 2.2.0
    • Testcase included:
      yes
    • Number of attachments :
      5

      Description

      JRuby script demonstrating the problem attached. Lucene 2.2.0 JAR also attached.

      1. exploder2.rb
        3 kB
        Bill Dortch
      2. lucene_exploder
        2 kB
        Scott Davies
      1. JRuby1.1.3-Memory.jpg
        75 kB
      2. JRuby1.1RC1-Memory.jpg
        79 kB

        Issue Links

          Activity

          Hide
          Vladimir Sizikov added a comment -

          Memory graph for JRuby 1.1RC1 running exploder2.rb script. This run was about 50% slower than JRuby 1.1.3, and GC time shows almost a minute!

          Show
          Vladimir Sizikov added a comment - Memory graph for JRuby 1.1RC1 running exploder2.rb script. This run was about 50% slower than JRuby 1.1.3, and GC time shows almost a minute!
          Hide
          Bill Dortch added a comment -

          Committed switch to OPC weak references in 5606. This limits the effectiveness of the cache; see forthcoming note at JRUBY-199. Leaving this issue open pending verification that switch to weak refs alone solves the problem.

          Show
          Bill Dortch added a comment - Committed switch to OPC weak references in 5606. This limits the effectiveness of the cache; see forthcoming note at JRUBY-199 . Leaving this issue open pending verification that switch to weak refs alone solves the problem.
          Hide
          Vladimir Sizikov added a comment -

          I can confirm that after the latest Bill's change, the memory consumption is back to normal, and memory is not constantly growing anymore.

          Also, exploder2 runs with the latest JRuby are now faster than JRuby 1.0.3 ones.

          Show
          Vladimir Sizikov added a comment - I can confirm that after the latest Bill's change, the memory consumption is back to normal, and memory is not constantly growing anymore. Also, exploder2 runs with the latest JRuby are now faster than JRuby 1.0.3 ones.
          Hide
          Charles Oliver Nutter added a comment -

          Fixed by Bill by making the proxy cache use weak references. I'll file a separate bug to address the efficacy of the cache.

          Show
          Charles Oliver Nutter added a comment - Fixed by Bill by making the proxy cache use weak references. I'll file a separate bug to address the efficacy of the cache.
          Hide
          Charles Oliver Nutter added a comment -

          Linking to the cache efficacy bug.

          Show
          Charles Oliver Nutter added a comment - Linking to the cache efficacy bug.

            People

            • Assignee:
              Charles Oliver Nutter
              Reporter:
              Scott Davies
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: