Hello,
There has been talk that the API can only handle 200 - 300 connections at a time and it bottlenecks if it goes higher. I ask because we experienced something similar during a big ticket sale last month (hundreds of people trying to hit the website at the same time). Has anyone experienced anything similar and if so how did you compensate for it?
Thanks for all of you who gave me input into the API. It is worth taking a look at the documentation to test the API. Not to mention possibly creating a waiting room at the checkout process.
Robert
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Ken McSwainSent: Wednesday, January 12, 2011 4:02 PMTo: Robert MartinSubject: Re: [Tessitura Technical Forum] Web API
Hi Robert
There is now a test hardness available for the API - documentation here - ;that will let you run diagnostic testing to see what load your api can actually handle. It only tests from the the API back, of course, not your website or any other front-end components, but it can give you basic information about what load your api can actually handle, and help you distinguish between api and website as a source of performance issues.
Ken
From: Robert Martin <bounce-robertmartin8728@tessituranetwork.com>Sent: 1/12/2011 2:44:54 PM
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!