[
https://issues.apache.org/jira/browse/AXIS2-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135346#comment-13135346
]
Jason Tholstrup edited comment on AXIS2-5119 at 10/25/11 7:25 PM:
------------------------------------------------------------------
Hi all,
I just recent ran into this issue when upgrading from axis 1.3. I saw a huge
performance hit when we upgraded. I patched a 1.6.0 version of axis with the
fix listed here and it improved our performance greatly. (As a side note it
merged in quite cleanly.) I think the difference in performance warrants
putting it into a 1.6.2 release instead of waiting for 1.7. We are currently
running on this patched jar but would love to get back to an official release.
Any thoughts on merging this into the 1.6 branch?
Below are my times with various axis implementations on the same call with a
700MB payload. (about 1000 objects) As you can see the unpatched 1.6 version
is a big step backwards.
Axis version _____ min time ___ max time _____ avg time (in ms)
Axis 1.3 _________ 1416 ______ 2975 ________ 2591
Axis 1.4 _________ 1500 ______ 3228 ________ 2690
Axis 1.6 _________ 5574 ______12160 ________ 7741
Axis 1.6 PATCHED __641________ 2231________ 1557
*Edit: Jira apparently doesn't whitespace formatting.
was (Author: jason tholstrup):
Hi all,
I just recent ran into this issue when upgrading from axis 1.3. I saw a huge
performance hit when we upgraded. I patched a 1.6.0 version of axis with the
fix listed here and it improved our performance greatly. (As a side note it
merged in quite cleanly.) I think the difference in performance warrants
putting it into a 1.6.2 release instead of waiting for 1.7. We are currently
running on this patched jar but would love to get back to an official release.
Any thoughts on merging this into the 1.6 branch?
Below are my times with various axis implementations on the same call with a
700MB payload. (about 1000 objects) As you can see the unpatched 1.6 version
is a big step backwards.
Axis version min time max time avg time (in ms)
Axis 1.3 1416 2975 2591
Axis 1.4 1500 3228 2690
Axis 1.6 5574 12160 7741
Axis 1.6 PATCHED 641 2231 1557
> ComplexType array return performance issue
> ------------------------------------------
>
> Key: AXIS2-5119
> URL: https://issues.apache.org/jira/browse/AXIS2-5119
> Project: Axis2
> Issue Type: Improvement
> Components: adb
> Affects Versions: 1.6.0
> Environment: Ubuntu 10.04 64-bit, Tomcat 6.0.28, Axis 1.6.0
> Reporter: Vilnis Termanis
> Labels: adb, array, arrays, complextype, performance
> Attachments: BeanUtil.java
>
>
> Service function returns which contain (long) arrays of custom objects
> degrade performance.
> Example (POJO):
> SomeCustomType[] myFunc() is a lot slower than String[] myFunc()
> Reason:
> BeanUtil.getBeanInfo()
> (modules/adb/src/org/apache/axis2/databinding/utils/BeanUtil.java) is called
> for each element in the output array, even though they are all the same.
> (According to
> http://download.oracle.com/javase/6/docs/api/java/beans/BeanInfo.html the
> result should be cached but this does not seem to be happening.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
