4 ms·
I’m not excusing the wild number, but just tossing out some additional load: * Drivers checking in for work, especially if the apps poll automatically * Drivers
by BrentOzar 3y ago
I’m not excusing the wild number, but just tossing out some additional load:
* Drivers checking in for work, especially if the apps poll automatically
* Drivers phoning home with live location updates
* Restaurants sending automated updates on order status
* Push notifications to users with status changes on their orders
* Users with multiple devices (like I have at least 5 devices with the UberEats app)
- deleted 3y ago[deleted]
- jakjak123 3y agoYes, our server had 120k queries/sec, but 80% of that traffic was driver heartbeats or connection verification. We halved it by disabling the connection verification query.
- javawizard 3y agoHold up, what do you mean by "our server"? Do you work for DoorDash?
- jakjak123 3y ago[dead]
- cdchn 3y agoEven just searching and browsing restaurants and menus is probably dozens of queries for every interaction.
- gizmo 3y agoSerializing json is pretty expensive at scale. I would be shocked if restaurant and menu json doesn't get cached aggressively.