> Seems like the real reason it performed worse in this simulation is that when they implemented destination dispatch, they assigned an elevator at time of request, and had no system for reviewing and updated that assignment.
I don't think it's possible to have destination dispatch AND update assignment together, in the real world.
- If the user clicks floor 26 and you tell them to wait at elevator G, you can't really tell them to move to F if it's taking too long.
- But if you don't tell them an elevator to wait at, then you'd need them to run around what is possibly like 5-8 elevators to find which one is going to their floor? That's obviously not realistic.
So then you're going to just have them get in the first one that opens? But then that's just the same as an up/down button.
That explanation is entirely inconsistent with sambellll's statement that when the user clicks a floor, the display tells them what elevator to take, and that elevator is then locked into going to that floor.
Also, I don't think that destination dispatch would work if the elevator didn't commit to going to the users's floor at the point the user got onboard. It may also stop at additional floors that weren't committed to when the user entered, and it may drop floors it was thinking of going to before it picked up the user (if the user onboard isn't going to those floors), but once the user gets onboard, that floor is a hard commitment.
I built an app a few years ago and needed some sort of DB to store around 50 million records that had ~10k reads+writes per month with 1 index. It cost me something like $50 to load it up initially, and then something stupid like 10 cents/month to maintain.
It is the same story over and over again. Your AWS bill is "low" because the actual resources you use are a tiny fraction of what a modern computer can deliver.
This is probably fine for your case, but you could run the same load on any toaster, and without a meaningfully demanding task it is hard to tell them apart.
Proximity doesn’t automatically result in interaction, though. If every one of those 100 people get in their private mobile room every time they leave their private mobile room there is no chance for any of them to interact.
I know which one works better for us. Which works better for grandma?
(Of course, Google's move shouldn't have been altruistic, it would have been pragmatic as mentioned elsewhere.)
If I got paid a nickel every time someone talked about protecting children online and I reinvested it into technology accessibility for seniors, it'd be fully funded! :)
I don't think it's possible to have destination dispatch AND update assignment together, in the real world.
- If the user clicks floor 26 and you tell them to wait at elevator G, you can't really tell them to move to F if it's taking too long.
- But if you don't tell them an elevator to wait at, then you'd need them to run around what is possibly like 5-8 elevators to find which one is going to their floor? That's obviously not realistic.
So then you're going to just have them get in the first one that opens? But then that's just the same as an up/down button.