Large GA Facility

We will be building a very large GA facility(60,000 seats).  Has anyone done something on this scale in Tess?   Besides the obvious issue of having many screens to page through, are there any other gotchas that I should be aware of?

Parents
  • Former Member
    Former Member $organization
    Hi Ed 
    We once built a quite large GA facility, purely for testing web performance (not as big as that, though). The main gotcha that we hit was that we assumed best seat zones would be irrelevant, and just made it all one big zone. Not a good idea. You need to chop it up into lots of little ones - at least one per screen, probably, or else the whole thing slows to a crawl, or a dead stop, actually. 

    Ken

    Sent from the iPad

    On 16/05/2012, at 3:57, "Ed Denning" <bounce-eddenning6733@tessituranetwork.com> wrote:

    We will be building a very large GA facility(60,000 seats).  Has anyone done something on this scale in Tess?   Besides the obvious issue of having many screens to page through, are there any other gotchas that I should be aware of?




    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!

    Visit our new website at www.aco.com.au

    This email is confidential. If you are not the intended recipient you must not disclose or use the information contained in it. If you have received this email in error please notify us immediately by return email and delete the document. The ACO is not responsible for any changes made to a document other than those made by the ACO or for the effect of the changes on the document's meaning. The ACO accepts no liability for any damage caused by this email or its attachments due to viruses interference, interception, corruption or unauthorised access.
  • I would just add that you should plan out what you will name the seat zones so that they are displayed in the correct order in reports.

    We recently built a Facility with over 20 zones, with the names representing entry times, and had issues with 12:00pm showing before 9:00am in TStats and a few other places.

    You can obviously tweak your reports to make sense of it, but its much better having the natural ordering being useful.

  • I agree with the best seat/zone issue. I built a 32,000 seat facility with one zone and then discovered there was no way the to do an order as it just crashed everytime you tried to best seat or even pick the seats in the seat map.

Reply Children
No Data