Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-1443

Stateless session bean invocation takes 30% longer with Weld 2.0

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: 2.0.0.Final
    • Fix Version/s: None
    • Component/s: Weld SPI
    • Labels:
      None
    • Environment:

      This is observed in Glassfish 4

    • Steps to Reproduce:
      Hide

      1. Deploy an application with a stateless session bean (@Stateless annotation) with CDI 1.1 implicit behavior disabled, and invoke the application to exercise the session bean.

      2. Deploy an application with a stateless session bean (@Stateless annotation), and invoke the application to exercise the session bean.

      3. Measure the difference in performance between the two; It's significant.

      Show
      1. Deploy an application with a stateless session bean (@Stateless annotation) with CDI 1.1 implicit behavior disabled, and invoke the application to exercise the session bean. 2. Deploy an application with a stateless session bean (@Stateless annotation), and invoke the application to exercise the session bean. 3. Measure the difference in performance between the two; It's significant.

      Description

      Micro benchmarks on EJB local session beans have regressed by 30% because of implicit CDI.

      The problem is that the WeldListener requestInitialized() and requestDestroyed() methods are consuming large amounts of CPU. These are all simple requests to call a business method on a stateless bean.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jharting Jozef Hartinger
                Reporter:
                phil.zampino Phil Zampino
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: