Details

    • Type: Wish Wish
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      We had a performance and profiler check on Axis2 when we released M1. But after that we couldn't do it.
      For testing AXIOM, we used Sosnoski's XML bench.
      IMO, its better to do these again, before we release 1.0.

        Issue Links

          Activity

          Hide
          Eran Chinthaka added a comment -

          Performance test already done and logged in here http://www.wso2.net/2006/05/axis2_performance_testing_round_1.

          Show
          Eran Chinthaka added a comment - Performance test already done and logged in here http://www.wso2.net/2006/05/axis2_performance_testing_round_1 .
          Hide
          Davanum Srinivas added a comment -

          Yep. Please don't close this.

          – dims

          Show
          Davanum Srinivas added a comment - Yep. Please don't close this. – dims
          Hide
          Eran Chinthaka added a comment -

          Hmm, I think Axiom perf check is just one part of this.

          We need to run some perf test on things like round trip time and memory and try to improve them. So lets not close this.

          Show
          Eran Chinthaka added a comment - Hmm, I think Axiom perf check is just one part of this. We need to run some perf test on things like round trip time and memory and try to improve them. So lets not close this.
          Hide
          Deepal Jayasinghe added a comment -

          Dims:
          I know that you did a great job to improve axom performance , I think we are in a position to close this issue.

          Show
          Deepal Jayasinghe added a comment - Dims: I know that you did a great job to improve axom performance , I think we are in a position to close this issue.
          Hide
          Dennis Sosnoski added a comment -

          Taking a look at the current AXIOM code, I can guarantee that the memory usage is going to be considerably higher than any of the standard document models for whatever portion of the tree actually gets built. The OMNodeImpl class alone has 4 object references, and int, and a boolean, for a minimum size of 21 bytes. The OMElementImpl class adds another 6 object references and 2 ints, for a mimum size of 53 bytes. OMTextImpl adds 7 object references and 2 booleans to OMNodeImpl, for a minimum size of 52 bytes. These are much larger than the equivalent classes from standard document models (JDOM, for instance, has 6 object references in its Element class, for a minimum size of 24 bytes, and just 2 object references in its Text class, for a minimum size of 8 bytes).

          Do you still have the XMLBench code you used for testing the M1 AXIOM? It's probably a good idea to try another test run as we're nearing the 1.0 release.

          Show
          Dennis Sosnoski added a comment - Taking a look at the current AXIOM code, I can guarantee that the memory usage is going to be considerably higher than any of the standard document models for whatever portion of the tree actually gets built. The OMNodeImpl class alone has 4 object references, and int, and a boolean, for a minimum size of 21 bytes. The OMElementImpl class adds another 6 object references and 2 ints, for a mimum size of 53 bytes. OMTextImpl adds 7 object references and 2 booleans to OMNodeImpl, for a minimum size of 52 bytes. These are much larger than the equivalent classes from standard document models (JDOM, for instance, has 6 object references in its Element class, for a minimum size of 24 bytes, and just 2 object references in its Text class, for a minimum size of 8 bytes). Do you still have the XMLBench code you used for testing the M1 AXIOM? It's probably a good idea to try another test run as we're nearing the 1.0 release.
          Hide
          Eran Chinthaka added a comment -

          Well, I was referring to the XMLBench to check the performance of AXIOM.

          Anyway we wanna do the Axis2 engine perf check too. Hope your approach will be fine on that.

          Show
          Eran Chinthaka added a comment - Well, I was referring to the XMLBench to check the performance of AXIOM. Anyway we wanna do the Axis2 engine perf check too. Hope your approach will be fine on that.
          Hide
          Dennis Sosnoski added a comment -

          In the above comment I was referring to my web services performance test, at http://www.sosnoski.com/presents/cleansoap/comparing.html I know this was used for some tests on Axis 1.2, and at first glance I assumed this was what you were referring to in the description. It's probably a decent starting point for Axis2 tests in any case, since it gives a baseline covering several different frameworks.

          Show
          Dennis Sosnoski added a comment - In the above comment I was referring to my web services performance test, at http://www.sosnoski.com/presents/cleansoap/comparing.html I know this was used for some tests on Axis 1.2, and at first glance I assumed this was what you were referring to in the description. It's probably a decent starting point for Axis2 tests in any case, since it gives a baseline covering several different frameworks.
          Hide
          Dennis Sosnoski added a comment -

          I can write a version of the test for Axis2/XMLBeans so that it'll be directly comparable with the Axis results. I think I'm missing some steps in how to actually start from WSDL and build both client and server versions of code using XMLBeans. Is this documented somewhere I've overlooked?

          I assume I want to start by generating XMLBeans classes from the WSDL, I'm just unclear on the details of hooking them in to Axis2 on both ends.

          Show
          Dennis Sosnoski added a comment - I can write a version of the test for Axis2/XMLBeans so that it'll be directly comparable with the Axis results. I think I'm missing some steps in how to actually start from WSDL and build both client and server versions of code using XMLBeans. Is this documented somewhere I've overlooked? I assume I want to start by generating XMLBeans classes from the WSDL, I'm just unclear on the details of hooking them in to Axis2 on both ends.

            People

            • Assignee:
              Davanum Srinivas
              Reporter:
              Eran Chinthaka
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development