The performance advantage of Axis2 over Axis(1) is mostly because Axis(1) converts every message to DOM form. Axis2 instead handles most data by using some form of data binding, which converts to and from Java objects with much better performance than a DOM. In cases where the full DOM representation is used (such as when WS-Security is involved), Axis2 uses AXIOM. I haven't actually tested this, but in these cases Axis2 might actually be slower than Axis(1), because AXIOM is slower and bulkier than most DOM models (see http://www.ibm.com/developerworks/webservices/library/ws-java2/ for some performance results).

The importance of StAX is not that it's much faster than SAX, but that it allows the SOAP framework to hand off processing of the document data to the data binding framework. The linked article discusses this in more detail.

 - Dennis

--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117



Venkat Reddy wrote:
Not answering the original question, but want to share a similar
question that I had in the beginning of Axis2 design - if the entire
content of a SOAP message is meant for consumption at various phases
by various components, the round-trip performance of message parsing
by StAX shouldn't be higher than that of SAX parser, at least
theoritically. After all, whether it is pull or push, I think every
xml chunk in the SOAP message has to be consumed somewhere during the
message processing.

I'm also delighted by the performance of Axis2 (great job folks), and
also like to know the reasons, probably not related to StAX parser.

thanks
Venkat


On Mon, Jun 16, 2008 at 4:07 PM,  <[EMAIL PROTECTED]> wrote:
Dear Keith,

Thanks for your reply.
We're aware that Axis2 is much faster than Axis1.X and we have conducted
similar tests as described in the articles.
Our question is, is the performance gain in Axis2 is due to the use of StAX
API? In my opinion StAX is not faster than SAX , so how come Axis2 is 5
times faster than Axis1.X? (We assumed the ADB binding part in Axis1.X
performs as well as Axis 2).

Best wishes,
Mai Sun
________________________________
From: keith chapman [mailto:[EMAIL PROTECTED]
Sent: 16 June 2008 11:48
To: [email protected]
Subject: Re: Does Axis2 provide much better performance than Axis 1.X?

Hi,

Here are some results of performance testing We've done. You can go through
these articles to see the reality (Axis2 is FAST).

http://wso2.org/library/91
http://wso2.org/library/588

Thanks,
Keith.

On Mon, Jun 16, 2008 at 2:43 PM, <[EMAIL PROTECTED]> wrote:
Hi,

Sorry for double posting…...

I read somewhere that Axis2 provides better performance comparing to Axis
1.X due to the introduction of StAX XML parsing. Based some tests, I can see
that for large XML document Axis2 is 5 to 10 times faster than Axis 1.X. I'm
a bit confused here since Axis1.X uses SAX parser which should be at least
as fast as StAX parser, so why the performance improvement is achieved?

Thanks a lot!

Regards,
Mai Sun
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to