Hi All,
Just recently we've been experiencing serious performance problems on our website. Looking into the logs it appears that "GetNewSessionKey" and "SetVariable" methods are frequently timing out. We recently upgraded to 12.5 but were experiencing performance problems before the upgrade. Site has been performing well for months but has suddenly ground to a halt. Any ideas what might be causing these methods to timeout?
Thanks
We had a similar problem. It was name resolution issue. You could try rather then using he host name use the IP. If you are on TNEW and RAMP I would open ticket. They could probably hunt it down rather quickly. Just thought.
Travis
Hi Huw,
Any time you troubleshoot performance issues, you want to isolate different parts of the stack. The basic pieces of the stack are (you can also have other things like firewalls and load balances):
Website -> API -> Database
Right now you believe the method of the API is slow. Therefore it could be the API or the Database.
You can try to isolate the database by running a profiler when you make the API call. The profiler will tell you how long the database portion of the stack takes. If the database is fast, then you've isolated the API server as your issue. If the database is slow, then you've isolated the database server.
Huw, my money is on your t_web_session_session table being too large. Have you checked the size of the table? If that's the problem, there's a utility that cleans it out, don't have the name on the tip of my tongue. You'll want to do it sooner rather than later, because we had our whole site collapse under these timeouts in the past.
We already use the IP for talking to the API so I don't think it's that.
The T_Web_Session_Session table was my first thought. We ran the clean up utility "UP_CLEAN_WEB_TABLES", which did significantly reduce our session table but performance issues remain.
Will run a profiler in the morning to to see if that casts any more light on the situation.
Thanks for feedback everyone. Let me know if there are any other ideas.
You might also want to make sure your timeout values in each of your configurations (CC, API Confg, IIS). The API and IIS would probably be most relevant ones. Make sure you chain them correctly, from lowest to highest.
This document has some recommended values:
http://www.tessituranetwork.com/knowledgebase/Content/Payment%20Processing/Timeout%20Recommendations%20for%20Credit%20Card%20Processing.htm
If the API config or IIS values are too low or not chained correctly, they might cause the timeouts you are seeing.
Thanks,
Patrick
Director of eCommerce Operations The Pittsburgh Cultural Trust 803 Liberty Avenue Pittsburgh, PA 15222 fitzgerald@trustarts.org 412.325.7061
Hi Huw
Re the timeout settings - we were having timeout issues with cc processing in v12.5, and adjusting the API timeouts seemed to have no effect, until someone noticed that there was a second timeout-setting line in another spot in the API config file. It was taking priority, so the changes that the guys were making were in fact non-functional. I believe it was a relic of some previous testing that hadn't been removed from the 12.5 download version.
Not likely to be your issue, I suspect, but worth checking.
Ken
Were having this problem too. anyone have any further suggestions?