Has anyone else experienced slow seat server performance when using packages?
We are not using RAMP, our servers are on-site. We recently began selling fixed GA + special exhibition packages using a GA facility and during our busier periods when multiple users are selling it can take up to 30 sec or more to add a package to a cart, and another 30 sec to print the tickets. At times it looks like the client is going to crash. There is a window that pops up in the lower left hand corner of the screen that says "Waiting for SeatServer". Definitely not ideal
I'm trying to figure out if this is an issue with set up or if it's linked to seat server performance. Any ideas?
Is your facility very large? We had trouble with our admissions facility being so big that it slowed things down when you tried to sell in a large amount of tickets. I initially built it much larger than it needed to be just in case we would use it for a future big event. When we corrected that it really helped!
It's about 14k seats, and we need it to be about that size because we can have pretty busy days. How large is your facility? Have you used packages at all?
Sorry, I just looked pack in my emails and realized I steered you wrong! The problem wasn't the size of our facility, but rather an unconfigured screen that we didn't realize was there. It was accidentally added during the facility setup, and didn't cause us problems until we would try to sell through many seats at once (we do this when we have free nights). Our Tessitura administrator was able to remove the extra screen, and that is what fixed our problem. She found this link helpful about facility troubleshooting.
https://www.tessituranetwork.com/Items/Videos/Training/Facility-Management
She used the add or remove seats from existing facilities video. This may not be your problem, but it is worth taking a look at your facility!
Ok, thanks! Will look into it.
What version of Tessitura are you using and are you on RAMP or self hosted?
Here at LSC we have seen some deadlock problems in Tessitura V15.0.x. These deadlocks were associated with slow down types of symptoms. Our facilities are in the 7-9K size
Have you looked at the standard error report in Tessitura to see if you are seeing anything?
Second, when we opened a TASK ticket we were able to work with the developer team to identify some of the potential problems. The Network Developers may have some fixes that they can share are part of some of the Service Packs that may help resolve your problems as well.
I'd open a TASK ticket if you have not already done so.