glassfish
  1. glassfish
  2. GLASSFISH-15412

[PERF] processApplication() needs improvement

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: performance
    • Labels:
      None

      Description

      We are looking at the long loading time that Admin Console user is experiencing.
      Jason did some measurement, and see that this one line of code

      > habitat.getComponent(ApplicationLoaderService.class).processApplication(config, ref, log);

      takes 18 seconds. Refer to GLASSFISH-15393.
      We need someone to look into this.
      I'll start with 'admin', please reassign if needed.

        Issue Links

          Activity

          Hide
          Hong Zhang added a comment -

          Tom: thanks for measuring the numbers on a Nigara system. I don't know about the particular order of the log messages, Anissa might have some insights on this. From your measurements, the GUI application loading times seems to be consistent with what Jason and I have seen, no signifant difference between DAS-only and cluster scecenarios, falling in 27.3 + 1.5 second range. Harshad has re-measured the numbers with the tracing turned on today, and his numbers are still pretty different for DAS-only and cluster scenario 7.119 vs 41.302 (see more details in issue 15393). From the finer tracing messages in the server.log, each step just takes much longer especially the container initialization and component loading. Do you have some idea what might be different? I have asked him to share more details on his set up.

          Show
          Hong Zhang added a comment - Tom: thanks for measuring the numbers on a Nigara system. I don't know about the particular order of the log messages, Anissa might have some insights on this. From your measurements, the GUI application loading times seems to be consistent with what Jason and I have seen, no signifant difference between DAS-only and cluster scecenarios, falling in 27.3 + 1.5 second range. Harshad has re-measured the numbers with the tracing turned on today, and his numbers are still pretty different for DAS-only and cluster scenario 7.119 vs 41.302 (see more details in issue 15393). From the finer tracing messages in the server.log, each step just takes much longer especially the container initialization and component loading. Do you have some idea what might be different? I have asked him to share more details on his set up.
          Hide
          Tom Mueller added a comment -

          One thing to check is the memory on the system. If it is memory starved, everything is going to take longer, and if several local instances are started, that will consume even more memory.
          The Niagra system I tested had plenty of memory (64GB or something like that).

          Show
          Tom Mueller added a comment - One thing to check is the memory on the system. If it is memory starved, everything is going to take longer, and if several local instances are started, that will consume even more memory. The Niagra system I tested had plenty of memory (64GB or something like that).
          Hide
          Nazrul added a comment -

          This problem exist on one specific platform. Excluding from 3.1 count. Lets look at this during 3.2.

          Show
          Nazrul added a comment - This problem exist on one specific platform. Excluding from 3.1 count. Lets look at this during 3.2.
          Hide
          scatari added a comment - - edited

          Issue isolated to the particular machine. Cannot reproduce anywhere else.

          Show
          scatari added a comment - - edited Issue isolated to the particular machine. Cannot reproduce anywhere else.
          Hide
          Hong Zhang added a comment -

          Closing the old issue as it was only reproducible on the particular sqe machine.

          Show
          Hong Zhang added a comment - Closing the old issue as it was only reproducible on the particular sqe machine.

            People

            • Assignee:
              Hong Zhang
              Reporter:
              Anissa Lam
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: