CODEWITHSUNDEEP
web-servicessoapcoldfusionapache-axiscoldfusion-10
Dan Roberts
Dan Roberts

Reputation: 4694

Why are my coldfusion soap webservices 10 times slower in production vs development?

UPDATE

It appears this issue is caused by a bug related specifically to using Axis2 with ColdFusion and we have been able to replicate the issue in our production environment on two different servers by switching between Axis1 and Axis2. My original tests to compare the two were apparently thwarted by an override in an Application.cfc which forced Axis2.

We ran into a memory leak today which forced us to speed up the resolution to this issue. It resembled the leak discussed here though we aren't sure if it is the exact same problem (https://www.hass.de/content/coldfusion-10-webservice-leaking-memory-trusted-cache-leaks-memory).

Our primary webservices are in Axis1 and we only switched to Axis2 for this new set of webservices because we needed document literal style for SalesForce and with Axis1 an invalid wsdl was being created (did not properly describe all object types in arrays). So now we have it as Axis1 and using a manually manipulated wsdl. Not entirely sure if it will work out with SalesForce but as far as a general fix this works.

I am investigating an issue with our coldfusion based soap webservices in our production environment. It appears that the time between the return statement in the webservices method code and actually receiving a response can be significant and appears to directly correspond to the size of the response and/or number of objects.

In development a particular request that returns 1000 records takes about 6 seconds to return. However in production that same hit takes 50+ seconds to return. I added some timing code and found that the actual function code takes less than 1 second to run at the start of the request, meaning that generating the response is taking coldfusion about 50 seconds in production. Hitting the webservice with simple http request does not have the same slowness so seems to be soap/axis specific. The resulting xml is about 1MB which I have compared and found no differences. I also copied out settings from cfadmin in both environments to compare and could find no performance related setting differences.

Both environments are at the same CF 10 update level. The server monitor shows no significant memory usage. I also ran the request from in the server to make sure there wasn't some slow connection issues or https slowing things down but the results are the same.

Any suggestions or solution would be appreciated.

Additional notes...

Upvotes: 2

Views: 674

Answers (1)

Mark A Kruger
Mark A Kruger

Reputation: 7193

One possibility is that you have them throttled - check the "request tuning" in your CF administrator. By default the setting for "number of simultaneous web service requests" is 10. Are you looping and hitting the server? In production is there more traffic?

In server monitor enable profiling and monitoring, then click on "statistics". On the far right there is a little chart icon. click on it and you will see a chart and a counter legend in the top right. Then run your code. Does the "web services running" reach a threshold and cross into "web services queued" - if so you need to increase that threshold.

enter image description here

One more clue - in the server monitor do NOT run the "memory profiling for more than a few seconds - say 30. If you don't you will have performance problems for sure.

Upvotes: 2

Related Questions