Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-4293

MemoryProfiler explicitly calls System.gc() and System.runFinalization() and Thread.sleep().

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • FUTURE
    • jBPM 6.1.0.Beta2
    • Dashboard Builder
    • None

    Description

      The Dashbuilder's MemoryProfiler (https://github.com/droolsjbpm/dashboard-builder/blob/master/modules/dashboard-commons/src/main/java/org/jboss/dashboard/profiler/memory/MemoryProfiler.java) explicitly calls System.gc(), System.runFinalization() and Thread.sleep(10) (twice) in it's 'collectGarbage()'.

      IMHO, explicitly calling System.gc() and Thread.sleep() in code is very bad practice. In this case it significantly slowed down the JBoss BPMSuite system because it was doing an enormous amount of (unnecessary) Full GCs.

      Attachments

        Activity

          People

            david.magallanes David Gutierrez
            rhn-gps-ddoyle Duncan Doyle (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: