You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by sean curtis <se...@yahoo.com> on 2007/03/07 00:27:51 UTC
Axis2 Client performance issue - AxisConfiguration Caching
When running some recent tests against our webserver that contains our client code, it seems that the client causes a huge bottleneck in performance. Perhaps we have it configured incorrectly, but doing some initial looking at the source code, the question came up:
When using the following code:
ConfigurationContext configContext = ConfigurationContextFactory.createConfigurationContextFromFileSystem(getAxis2RepositoryPath(), getAxis2ConfigFileLocation());
does this actually cause a re-parse, reconfigure of the axis2.xml file on each call? If so, that seems to point to a massive performance bottleneck in saying we have to parse a basically static file every time we want to call our services.
As I said, we might have it configured incorrectly, but this came up as a possible issue. Can anyone shed light? Is there a setting we can use to let it cache this configuration?
thanks
____________________________________________________________________________________
No need to miss a message. Get email on-the-go
with Yahoo! Mail for Mobile. Get started.
http://mobile.yahoo.com/mail
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 Client performance issue - AxisConfiguration Caching
Posted by Davanum Srinivas <da...@gmail.com>.
You can cache configContext itself!
-- dims
On 3/6/07, sean curtis <se...@yahoo.com> wrote:
> When running some recent tests against our webserver that contains our client code, it seems that the client causes a huge bottleneck in performance. Perhaps we have it configured incorrectly, but doing some initial looking at the source code, the question came up:
>
> When using the following code:
>
> ConfigurationContext configContext = ConfigurationContextFactory.createConfigurationContextFromFileSystem(getAxis2RepositoryPath(), getAxis2ConfigFileLocation());
>
> does this actually cause a re-parse, reconfigure of the axis2.xml file on each call? If so, that seems to point to a massive performance bottleneck in saying we have to parse a basically static file every time we want to call our services.
>
> As I said, we might have it configured incorrectly, but this came up as a possible issue. Can anyone shed light? Is there a setting we can use to let it cache this configuration?
>
> thanks
>
>
>
>
>
>
> ____________________________________________________________________________________
> No need to miss a message. Get email on-the-go
> with Yahoo! Mail for Mobile. Get started.
> http://mobile.yahoo.com/mail
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2 Client performance issue - AxisConfiguration Caching
Posted by ar...@gmail.com.
Curtis,
I faced the same problem. It also leaks around 250KB per call. Though I
couldn't figure out the root set that is holding references to a lot
of OMElementImpl and OMTextImpl objects. The JVM was also crashing
every few days. Change the code generated to cache the
ConfigurationContext and the performance+memory leak disappears. In a
local loopback test the time taken to answer a request went down from
1.5s to around 20~50ms.
Cheers
Aravind
On 3/6/07, sean curtis <se...@yahoo.com> wrote:
> When running some recent tests against our webserver that contains our client code, it seems that the client causes a huge bottleneck in performance. Perhaps we have it configured incorrectly, but doing some initial looking at the source code, the question came up:
>
> When using the following code:
>
> ConfigurationContext configContext = ConfigurationContextFactory.createConfigurationContextFromFileSystem(getAxis2RepositoryPath(), getAxis2ConfigFileLocation());
>
> does this actually cause a re-parse, reconfigure of the axis2.xml file on each call? If so, that seems to point to a massive performance bottleneck in saying we have to parse a basically static file every time we want to call our services.
>
> As I said, we might have it configured incorrectly, but this came up as a possible issue. Can anyone shed light? Is there a setting we can use to let it cache this configuration?
>
> thanks
>
>
>
>
>
>
> ____________________________________________________________________________________
> No need to miss a message. Get email on-the-go
> with Yahoo! Mail for Mobile. Get started.
> http://mobile.yahoo.com/mail
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org