This is a call to ask if anyone has a figure for a "typical" checkout API call to complete, that they can share. Ours takes 7 to 10 secs, which we believe is rather on the long side of average.
Our ticketing servers and our web api server are all part of the same virtual cluster, so communication problems here should not be an issue.
We're looking to optimise all the elements in our checkout path: API server, DB server, CC Server and all the connections between and from our CC server to our processor, so if anyone has any tips that have worked for them it would be great to hear.
Thanks, Christopher
Hi Christopher,
I did a quick test here by purchasing two tickets and a donation on our test website.
From the time I clicked checkout to the time I got the confirmation page took about 40 seconds.
Our website server is hosted externally to our Tessitura API server so there is a delay here and there would be other functions running around this too so the actual Web API call would have taken less but still much more than the 7 to 10 seconds you have.
There would also have been a call to CommsXL to authorise the credit card during that.
I hope this information is of some help to you.
cheers,
Dara