Re: Axis2 Client performance issue - AxisConfiguration Caching
Ok, I'll do that for us ;) If this isnt added to the next release, hopefully everyone who uses axis2 as a client reads this and gets the benefit of OOM better performance and elminating a pervasive memory leak problem. - Original Message From: Davanum Srinivas [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Tuesday, March 6, 2007 6:32:42 PM Subject: Re: Axis2 Client performance issue - AxisConfiguration Caching You can cache configContext itself! -- dims On 3/6/07, sean curtis [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 Client performance issue - AxisConfiguration Caching
Sean, how could the factory cache a previously created instance since you can use different parameters for different calls? Michele On Wed, 2007-03-07 at 06:36 -0800, sean curtis wrote: Ok, I'll do that for us ;) If this isnt added to the next release, hopefully everyone who uses axis2 as a client reads this and gets the benefit of OOM better performance and elminating a pervasive memory leak problem. - Original Message From: Davanum Srinivas [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Tuesday, March 6, 2007 6:32:42 PM Subject: Re: Axis2 Client performance issue - AxisConfiguration Caching You can cache configContext itself! -- dims On 3/6/07, sean curtis [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 Client performance issue - AxisConfiguration Caching
without knowing all entailed ( and thus the reason I was asking why axis2 didnt attempt to do this) I'd guess solving that problem with something like: ConfigurationContext config = ConfigurationContextFactory.getCachedConfiguration( String differentParameter ) would be a problem worth understanding and solving to get this performance/memory management for all axis2 users was my only point. How varied that parameter set can be I guess is more the question, but when people are calling: ConfigurationContextFactory.createConfigurationContextFromFileSystem(getAxis2RepositoryPath(), getAxis2ConfigFileLocation()); (in a usual config situation) If nothing else, putting this functionality into some sort of base axis 2 client would be a huge gain. On a side note, we noticed the same sort of issues when hotdeploy was enabled. On the server side, is it doing the same thing? We're seeing the same issues, with degraded performance and seeming to leak memory? - Original Message From: Michele Mazzucco [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Wednesday, March 7, 2007 9:45:09 AM Subject: Re: Axis2 Client performance issue - AxisConfiguration Caching Sean, how could the factory cache a previously created instance since you can use different parameters for different calls? Michele On Wed, 2007-03-07 at 06:36 -0800, sean curtis wrote: Ok, I'll do that for us ;) If this isnt added to the next release, hopefully everyone who uses axis2 as a client reads this and gets the benefit of OOM better performance and elminating a pervasive memory leak problem. - Original Message From: Davanum Srinivas [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Tuesday, March 6, 2007 6:32:42 PM Subject: Re: Axis2 Client performance issue - AxisConfiguration Caching You can cache configContext itself! -- dims On 3/6/07, sean curtis [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. http://tools.search.yahoo.com/toolbar/features/mail/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 Client performance issue - AxisConfiguration Caching
In our case, both the parameters don't change at all so I made it into a class variable. I am not sure whether it is multi-thread safe but should be ok since it is a read-only object tree. If the parameters do change just use the tuple (path, axis2xml) as key and ConfigurationContext as the key value. Cheers Aravind On 3/7/07, Michele Mazzucco [EMAIL PROTECTED] wrote: Sean, how could the factory cache a previously created instance since you can use different parameters for different calls? Michele On Wed, 2007-03-07 at 06:36 -0800, sean curtis wrote: Ok, I'll do that for us ;) If this isnt added to the next release, hopefully everyone who uses axis2 as a client reads this and gets the benefit of OOM better performance and elminating a pervasive memory leak problem. - Original Message From: Davanum Srinivas [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Tuesday, March 6, 2007 6:32:42 PM Subject: Re: Axis2 Client performance issue - AxisConfiguration Caching You can cache configContext itself! -- dims On 3/6/07, sean curtis [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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]
Re: Axis2 Client performance issue - AxisConfiguration Caching
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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
