larryz
I'm Just A Tourist!
Just tell your boss you have a bad case of the RotRohs...
-
Welcome to the WDWMAGIC.COM Forums!
Please take a look around, and feel free to sign up and join the community.
News Star Wars: Rise of the Resistance Standby Line and Boarding Groups at Disney's Hollywood Studios
- Thread starter wdwmagic
- Start date
Indeed, we're now in the time period wherein for most days, the ride had significant stoppages.
Clyde Birdbrain
Unknown Member
80
FYI: You can see this in the app by tapping the ”Find Out More” button on the home screen.
Only if you use your Scooby Doo voice when saying RotRohs.
flynnibus
Premium Member
It's not about how many people as much as it's about lots of people all trying to do the same thing in a short amount of time. During normal park ops there is high usage, but it's mostly randomized and doing lots of different things. This is thousands of people in a race to do the same exact thing in a very short period of time.
Completely different challenges from a design perspective. The network and front-end infrastructure is already built up to support many many many more clients simultaneously. The problem is everyone focusing on their client on the same task.. for the same resource.
BoarderPhreak
Well-Known Member
Finally got around to processing some opening day photos.
Here's the crowd/progression from opening day... I was basically at the very front of the line.
Here's the crowd/progression from opening day... I was basically at the very front of the line.
Last edited:
On track for a personal best!
Kamikaze
Well-Known Member
I disagree. Hitting the same DB (or section of a DB) is going to be less resource intensive than spreading the load out across multiple. If it was my project, I would have spun up a separate AWS instance just for this, completely separate from everything else.
disneygeek90
Well-Known Member
That's right, they had a brand new recorded announcement talking about how BG's will be released at 7. That makes me think it wasn't just a one day thing.
AshaNeOmah
Well-Known Member
Things are looking good for improvement through Christmas Week. I wonder when they anticipate full capacity to occur? If they're still keeping 100 guests per group, they still haven't hit 13k in a single day, right? Only 65% of maximum capacity...
flynnibus
Premium Member
Simply put.. no. First, your idea would maybe make sense if it were a read-only system... but it's not.
Second AWS is just infrastructure... it is not data design nor does it speak to the kind of checks the backend would go through (that can't be decoupled from the rest of your MDE-universe) before it would grant people slots.
Third... the original comment was about the idea of contention... vs your stated reference of just general traffic levels.
disneygeek90
Well-Known Member
I was getting some errors in my drop/add process this morning, but I was trying to book a group literally seconds after dropping it. After a couple more seconds it would update and give me a new group, overall pretty impressed in how quick it registered both the add and the drop.
Kamikaze
Well-Known Member
A separate instance of AWS (or Google Cloud or Azure) would keep the boarding groups confined to one database, and you would only need the single button on MDE to point to that instance. That is the setup they currently have. You can't see the groups anywhere else in the app. Its trivial to route a button on an app to another site/DB. I would have done it separately because you can set the resources to peak in the periods around park open and then dial it back for the rest of the day, and not have to worry about potentially compromising the rest of the system due to the peak load.
There are only 4 points of data passed between MDE proper and the boarding groups:
1) Do you have a valid scanned in ticket?
2) Are you in the park?
3) Who is in your party?
4) Are you already in a boarding group?
3 of the 4 only have to be checked a single time - when you are put in a group - and only have to be passed one way. For a SQL query, thats actually a super simple check and very little data. I'd actually be shocked if the groups aren't a separate DB, because once they stop the groups here, they can reuse them for another ride in the future if its standalone.
Since the groups go in order, the BG DB itself would be simple - each group is 100 or whatever, and it contains the Magic Band RFID# and the number you scanned in numerically. Much, much less complicated than the FastPass database is since people can go in and out of those and change times all over the place.
donsullivan
Premium Member
Any word on whether the switchback queue in the hangar bay returned today, or did sanity prevail and they removed it overnight?
disneygeek90
Well-Known Member
I'll keep you posted on how it's looking in a few hours.
BG 97 was just called, I need to be back by 5:50.
Kamikaze
Well-Known Member
I would hope its removed, but I don't really have a problem with them trying it. They need to do T&A to figure out what works and what doesn't work, and temporary things like a switchback may happen.
TimeTrip
Well-Known Member
This penalizes hard-core locals. As a local that wouldn't ride it more than 2-3 times a month, I wouldn't mind it as it would thin out some of the crowds that make me less likely to try to get that first experience in. I'm not saying that it's the right approach, just that it would benefit some locals
