←back to thread

Upgrading Uber's MySQL Fleet

(www.uber.com)
234 points benocodes | 1 comments | 14 Oct 24 12:08 UTC | HN request time: 0s | source
Show context
remon ◴[14 Oct 24 14:48 UTC] No.41838059[source]▶
Impressive numbers at a glance but that boils down to ~140qps which is between one and two orders of magnitude below what you'd expect a normal MySQL node typically would serve. Obviously average execution time is mostly a function of the complexity of the query but based on Uber's business I can't really see what sort of non-normative queries they'd run at volume (e.g. for their customer facing apps). Uber's infra runs on Amazon AWS afaik and even taking some level of volume discount into account they're burning many millions of USD on some combination of overcapacity or suboptimal querying/caching strategies.
replies(5): >>41838139 #>>41838199 #>>41838202 #>>41839045 #>>41839409 #
nunez ◴[14 Oct 24 15:03 UTC] No.41838199[source]▶
Didn't realize their entire MySQL data layer runs in AWS. Given that they went with basically a blue-green update strategy, this was, essentially a "witness our cloud spend" kind of post.
replies(1): >>41838349 #
pocket_cheese ◴[14 Oct 24 15:20 UTC] No.41838349[source]▶
They're not. Almost all of their infra was on prem when I worked there 3 years ago.
replies(1): >>41838402 #
1. remon ◴[14 Oct 24 15:26 UTC] No.41838402{3}[source]▶
It's neither. I remember them moving to the cloud but apparently they moved to Google/Oracle (the latter making this article particularly interesting btw). As per the relevant press release : "It’s understood that Uber will close down its own on-premises data centers and move the entirety of its information technology workloads to Oracle and Google Cloud."