Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-15198

Avoid unneeded TimerImpl instances during db refresh

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 25.0.0.Beta1, 25.0.0.Final
    • None
    • EJB
    • None

      For ejb timers with database persistence, during a db refresh, many TimerImpl instances are created from query ResultSet, and many of them are not actively used. They are subsequently thrown away and gc'ed, which increases the gc burden.

      We should only create TimeImpl instances from ResultSet when really needed.

            cfang@redhat.com Cheng Fang
            cfang@redhat.com Cheng Fang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: