It doesn'tsemtex1871 wrote:This wouldn't happen in hospitality etc etc
There is a plan, although obviously if everyone had a card with a dodgy chip, or the central database got corrupted it would be chaos.Royal Biscuitman wrote:It shouldn't happen but at the same time, the club should have a plan in place if it does.... What happens if the electronic system crashes before the game? - I imagine there will be a delayed kick off as 18,000 fans queue up to see one ticket lady.
It's better than that - I'm pretty sure each turnstile is autonomous and can work offline once loaded with event data.Nameless wrote:18,000 wouldn't have to see one person as there are staff at each gate. The whole system can't crash as data is held at each gate, not on a central server.
Pretty certain it's per gate not per turnstile, and that is a change from when the system was first installed . Originally the server at the gate had to refer back to the central database for every query whereas now there is a copy held locally at each gate making it quicker and more resilient. Every gate is one of a pair so if say gate 7 went down they could use gate 8 for everyone, or go to a visual check at the turnstiles which wouldn't be 100% but ok as an emergency.EPR2.0 wrote:It's better than that - I'm pretty sure each turnstile is autonomous and can work offline once loaded with event data.Nameless wrote:18,000 wouldn't have to see one person as there are staff at each gate. The whole system can't crash as data is held at each gate, not on a central server.
When Fortress was first installed I initially wondered why each gate had a computer per turnstile (the blue boxes up on the wall) thinking that it was massively over-engineered; then it occurred to me, that the last thing you want when trying to ingress 24,000 people into a stadium is for an entire gate (or more) to go down just because of a single point of failure.
I think the laugh is on you, after all you are reading it !moo wrote:Are you guys seriously talking about this? Lul
Must be every gate not turn style otherwise what's to stop someone with a ticket for gate 4 using it on the left turn-style and passing it though to a mate to use on the right turn style, either that or they are linked but capable of working alone if one goes down.EPR2.0 wrote:It's better than that - I'm pretty sure each turnstile is autonomous and can work offline once loaded with event data
If an entire gate goes autonomous you still lose pass-back protection because of the "pairing" nature of the higher level redundancy. Individual turnstiles of an "offline" gate can still prevent pass-back over the gate's own [very] local area network as they probably do in normal operation, on which basis I would have thought it would make sense for a single build where each turnstyle computer is identical and holds the entire event data for that gate - I don't see the point in having a separate server per gate (or designating one of the turnstyle's computer as a local server) as you're back to a single point of failure per gate.Royal Biscuitman wrote:Must be every gate not turn style otherwise what's to stop someone with a ticket for gate 4 using it on the left turn-style and passing it though to a mate to use on the right turn style, either that or they are linked but capable of working alone if one goes down.EPR2.0 wrote:It's better than that - I'm pretty sure each turnstile is autonomous and can work offline once loaded with event data
Actually, they must all be linked so that attendance can be calculated and monitored, but as suggested above, capable of going it alone in the event of the network crashing
What kind of server were we using that would struggle with 20,000 checks in two hours?Nameless wrote: Originally the server at the gate had to refer back to the central database for every query whereas now there is a copy held locally at each gate making it quicker and more resilient.
Are you actually trying to suggest that the flow of people through the turnstiles is 20,000 spread even remotely evenly over 2 hours?tmesis wrote:What kind of server were we using that would struggle with 20,000 checks in two hours?Nameless wrote: Originally the server at the gate had to refer back to the central database for every query whereas now there is a copy held locally at each gate making it quicker and more resilient.
Users browsing this forum: No registered users and 122 guests