[prev in list] [next in list] [prev in thread] [next in thread]
List: sandesha-dev
Subject: Re: Improving JAX-WS Performance
From: Isuru Suriarachchi <isurues () gmail ! com>
Date: 2011-11-30 13:39:56
Message-ID: CAAtbvNX9d1VXjQ9rJLmB-=29vy4-kyjs9ROhbd9z=abBaiUc-Q () mail ! gmail ! com
[Download RAW message or body]
Hi Charith,
+1 for putting some more effort on improving our JAX-WS support. I'll
commit the proper fix to [1] ASAP and that will remove the bottleneck in
the JAX-WS MR. And also there'll be more places at which we can do
improvements to gain even better performance numbers.
Thanks,
~Isuru
[1] https://issues.apache.org/jira/browse/AXIS2-4930
On Tue, Nov 29, 2011 at 4:51 PM, Charith Wickramarachchi <
charith.dhanushka@gmail.com> wrote:
> Hi Devs ,
>
> JAX-WS is becoming a popular key webservice development style. While
> supporting its own web-service development/deployment style i think Axis2
> should improve its JAX-WS implementation. I started to profile Axis2 JAX-WS
> implementation having performance improvement in mind and was able to
> isolate a major bottleneck in this flow. (See the attached profile image.)
> Here the bottleneck was AXOM creating a XMLOutput factory per each
> invocation due to a bug in JAXWSMessageReceiver. I submitted a fix for this
> in[1]. And we are currently in the process of discussing on a proper
> solution for that issue.
>
> With this patch i was able to get ~75% performance improvement on Simple
> Echo jax-ws services and ~60% improvement with services with complex types.
>
>
> With this observation i think if we spend some energy on improving Axis2
> JAX-WS performance we will be able to improve it a lot and
> if we can publish that improved numbers may be with comparisons that will
> add a great value to this project.
>
> So i though of starting a discussion around it to discuss on how to
> improve this and areas we must focus on.
>
>
> [1]https://issues.apache.org/jira/browse/AXIS2-5203
>
> thanks,
> Charith
>
> --
> Charith Dhanushka Wickramarachchi
> http://charithwiki.blogspot.com/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
--
Technical Lead,
WSO2 Inc. http://wso2.org/
Blog : http://isurues.wordpress.com/
[Attachment #3 (text/html)]
Hi Charith,<div><br></div><div>+1 for putting some more effort on improving our \
JAX-WS support. I'll commit the proper fix to [1] ASAP and that will remove the \
bottleneck in the JAX-WS MR. And also there'll be more places at which we can do \
improvements to gain even better performance numbers.</div> \
<div><br></div><div>Thanks,</div><div>~Isuru</div><div><br></div><div>[1] <meta \
http-equiv="content-type" content="text/html; charset=utf-8"><a \
href="https://issues.apache.org/jira/browse/AXIS2-4930">https://issues.apache.org/jira/browse/AXIS2-4930</a><br>
<br><div class="gmail_quote">On Tue, Nov 29, 2011 at 4:51 PM, Charith \
Wickramarachchi <span dir="ltr"><<a \
href="mailto:charith.dhanushka@gmail.com">charith.dhanushka@gmail.com</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;"> Hi Devs , <br><br>JAX-WS is becoming a popular key \
webservice development style. While supporting its own web-service \
development/deployment style i think Axis2 should improve its JAX-WS implementation. \
I started to profile Axis2 JAX-WS implementation having performance improvement in \
mind and was able to isolate a major bottleneck in this flow. (See the attached \
profile image.)<br>
Here the bottleneck was AXOM creating a XMLOutput factory per each invocation due to \
a bug in JAXWSMessageReceiver. I submitted a fix for this in[1]. And we are currently \
in the process of discussing on a proper solution for that issue. <br>
<br>With this patch i was able to get ~75% performance improvement on Simple Echo \
jax-ws services and ~60% improvement with services with complex types. <br><br>With \
this observation i think if we spend some energy on improving Axis2 JAX-WS \
performance we will be able to improve it a lot and <br>
if we can publish that improved numbers may be with comparisons that will add a great \
value to this project. <br><br>So i though of starting a discussion around it to \
discuss on how to improve this and areas we must focus on.<br>
<br><br>[1]<a href="https://issues.apache.org/jira/browse/AXIS2-5203" \
target="_blank">https://issues.apache.org/jira/browse/AXIS2-5203</a><br> \
<br>thanks,<br>Charith<br><font color="#888888"><br>-- <br>Charith Dhanushka \
Wickramarachchi<br> <a href="http://charithwiki.blogspot.com/" \
target="_blank">http://charithwiki.blogspot.com/</a><br> <br>
</font><br><br>
---------------------------------------------------------------------<br>
To unsubscribe, e-mail: <a \
href="mailto:java-dev-unsubscribe@axis.apache.org">java-dev-unsubscribe@axis.apache.org</a><br>
For additional commands, e-mail: <a \
href="mailto:java-dev-help@axis.apache.org">java-dev-help@axis.apache.org</a><br></blockquote></div><br><br \
clear="all"><div><br></div>-- <br>Technical Lead,<br>WSO2 Inc. <a \
href="http://wso2.org/">http://wso2.org/</a><br> Blog : <a \
href="http://isurues.wordpress.com/">http://isurues.wordpress.com/</a><br> </div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic