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?
The first large on sale we crashed our system and, since we are part of Salt Lake County, we crashed their website because we got so many hits in a short period of time. After that, we had POP create a waiting room for our website so that we could handle large ticket sales. We can control how many people are allowed in to purchase at one time. You also need to consider how many transactions your credit card server can handle at a time.
Trudy Guest,
ArtTix Systems Administrator
801.323.6969
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Robert Martin Sent: Wednesday, January 12, 2011 1:47 PM To: Trudy Guest Subject: [Tessitura Technical Forum] Web API
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!
We rarely have major onsales, but we did recently for the Dalai Lama (we sold all 700 tickets we had remaining almost immediately, so the concurrent connections was probably several times that). Nothing crashed, but the system did become extremely slow (it took about 12 minutes for customers to go through the whole purchase path). If we needed to do something like that again, we would probably want to think about some kind of waiting room functionality.
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
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
From: Robert Martin <bounce-robertmartin8728@tessituranetwork.com>Sent: 1/12/2011 2:44:54 PM
We had a large on sale this past fall that stressed our environment. While we did have some bottlenecks with the Web API, our bigger problem was with the seat server.
Our web site currently only enforces per line item limits on the number of tickets. What we ran into was web patrons were adding multiple sets of seats to their cart in an attempt to find "better" seats, and then would abandon their cart which would leave the seats locked until they timed out. This caused some stress on the seat server.
We are working with our web integrator on a waiting room as well as some better ticket limit enforcement to reduce these issues for our next major on sale.
-steve carlock
Information Technology Manager
The Granada
(805) 899-3000 x 111 (phone)
(805) 899-3081 (fax)
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Robert MartinSent: Wednesday, January 12, 2011 12:47 PMTo: Steve CarlockSubject: [Tessitura Technical Forum] Web API