Hi Paul
Few results
We were able to bring down the response time to some extent by the following
measures
a) We observed that the load balancers were taking some time so we disabled
them and observed that the
response reduced by 80ms. These load balancers were hardware devices and
not done by the loading
balancing through Apache web server. This brings out a very interesting
question that should we have hardware
load balancers or do it through the web servers itself.
b) We reduced the logging levels and observed that there was some improvement
when we did not log details in
the logs.
c) We also observed that by removing the Apache web server itself and letting
the request directly hit the Jboss
application server where Axis2 is installed saved another 10ms. Although it
is not a good practise but we just
wanted to see how much time is being consumed by each layer.
so from 250ms per request we have narrowed down to 78-90ms on an average.
It was also observed that the Linux based systems are consuming more time
compared to windows based systems !! surprise surprise .......
and as i mentioed earlier also that i was sending the requests in ajax style to
achieve REST based services. Sending POX through javascript.
Soap and REST responses did not vary much there is difference of only 4ms.
Do let me know your throughts please
Vibhor
________________________________
From: Paul Fremantle [mailto:[EMAIL PROTECTED]
Sent: Sun 6/10/2007 4:46 AM
To: axis-user@ws.apache.org
Subject: Re: ****************Performance issues (Important)*****************
Deepal
If you read the note the problem isn't with REST performance. The
problem that Vibhor is having is that a standard SOAP call is taking
1s per request.
Paul
On 6/10/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> Hi Paul,
> From 1.1.1 to there was a major change by introducing WSDL 2.0 REST
> handling , as I can see that might me the issue here. Keith any idea
> about this ?
>
> Thanks
> Deepal
>
> Paul Fremantle wrote:
> > Vibhor
> >
> > There is something SERIOUSLY wrong going on here. Normally Axis2 1.1.1
> > could handle that request in less than 35ms (unless this is running on
> > a 386sx20Mhz PC :-)).
> >
> > See this performance data:
> >
> > http://wso2.org/library/588
> >
> > I can't imagine why its taking 1sec. Can you do some simple
> > benchmarking and see how long its taking to do the standard Version
> > request/response or one of the other samples? That would let us know
> > if its something with your network/OS/JDK or something with your app.
> >
> > Thanks
> > Paul
> >
> > On 6/8/07, Vibhor_Sharma <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >>
> >> The previous request was
> >>
> >>
> >>
> >> POST /Gryphon/RegulatoryService.asmx/CertifyPhoneNumber
> >> HTTP/1.1
> >>
> >> Host: ws.gryphonnetworks.com
> >>
> >> Content-Type: application/x-www-form-urlencoded
> >>
> >> Content-Length: length
> >>
> >> License=AAAA-BBBB-0000-1111-CCCC-2222-DD33-
> >>
> >> E44E&Number=5551110000&Verbose=1
> >>
> >> The new request is
> >>
> >>
> >> <cer:certifyContact
> >> xmlns:cer="http://webservices.gryphonnetworks.com/certify";
> >>
> >> xmlns:xsd="http://valueobjects.webservices.gryphonnetworks.com/xsd";
> >> >
> >>
> >> <cer:cinfo>
> >>
> >> <xsd:clientUserID>1123</xsd:clientUserID>
> >>
> >> <xsd:licenseID>C1CC-680E-ABF9-45F8-A0A1-EB4F-2950-90A8</xsd:licenseID>
> >>
> >> <xsd:verbosity>1</xsd:verbosity>
> >>
> >> <xsd:channelData>
> >>
> >> <xsd:channelType>Phone</xsd:channelType>
> >>
> >> <xsd:phoneNumber>7569872345</xsd:phoneNumber>
> >>
> >> </xsd:channelData>
> >>
> >> <xsd:channelData>
> >>
> >> <xsd:channelType>Phone</xsd:channelType>
> >>
> >> <xsd:phoneNumber>4563456783</xsd:phoneNumber>
> >>
> >> </xsd:channelData>
> >>
> >> </cer:cinfo>
> >>
> >> </cer:certifyContact>
> >>
> >> the previous request took 35 msec and the new request takes around 1
> >> second.
> >> Has it to do with the big XML packet?
> >>
> >> Vibhor
> >>
> >> ________________________________
> >> From: Paul Fremantle [mailto:[EMAIL PROTECTED]
> >> Sent: Fri 6/8/2007 2:41 PM
> >> To: axis-user@ws.apache.org
> >> Subject: Re: ****************Performance issues
> >> (Important)*****************
> >>
> >>
> >>
> >>
> >> Vibhor
> >>
> >> Can you give us some idea of the performance you are seeing and the
> >> requirements.
> >> Also what size of messages are you using? Also what databinding?
> >>
> >> By the way Axis2 also supports GET requests.
> >>
> >> Paul
> >>
> >> On 6/8/07, Vibhor_Sharma <[EMAIL PROTECTED]> wrote:
> >> >
> >> >
> >> > Hi
> >> > There has been latest releases of Axis2 recently has there
> >> been any
> >> > performance improvement since 1.1.1?
> >> >
> >> > I'm currently using Axis2 1.1.1 are there any significant
> >> improvements in
> >> > the response times?
> >> >
> >> > As of now we have deployed the web services in production and one
> >> of our
> >> > cutsomer is reluctant to move to the new release (based on AXIS2)
> >> as there
> >> > is performance degradation that he is seeing. He was earlier using
> >> REST
> >> > based services (GET mechanism ) and the request paremeters were
> >> being sent
> >> > along with the URL itself. This architecture was based on DOT NET
> >> > technology.
> >> >
> >> > We upgraded to the new architecure based upon Axis2.
> >> > One of the few things we have done is introduced a better structured
> >> schema
> >> > (usage of complex data types).
> >> > We have requested the client to to send the request through XML
> >> over HTTP
> >> > (using name spaces) using POST mechanism. The web services is invoked
> >> > properly but with the deterioration in performance. Any reason why
> >> this is
> >> > happening ? or any assistance you can give.
> >> >
> >> > This is really urgent.
> >> >
> >> > Vibhor
> >>
> >>
> >> --
> >> Paul Fremantle
> >> Co-Founder and VP of Technical Sales, WSO2
> >> OASIS WS-RX TC Co-chair
> >>
> >> blog: http://pzf.fremantle.org <http://pzf.fremantle.org/>
> >> [EMAIL PROTECTED]
> >>
> >> "Oxygenating the Web Service Platform", www.wso2.com
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >>
> >
> >
>
> --
> Thanks,
> Deepal
> ................................................................
> "The highest tower is built one brick at a time"
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org <http://pzf.fremantle.org/>
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
