3 million queries/second across 16k nodes seems pretty heavy on redundancy?
That doesn't sound unreasonable, on average. But I suspect the distribution is likely pretty uneven.
61–70 of 215 posts
3 million queries/second across 16k nodes seems pretty heavy on redundancy?
That doesn't sound unreasonable, on average. But I suspect the distribution is likely pretty uneven.
I can tell from a mile away that this is written by ChatGPT / Claude, at least partially. "This distinction played a crucial role in our upgrade planning and execution strategy." "Navigating Challenges in the MySQL Upgrade Journey" "Finally, minimizing manual intervention during the upgrade process was crucial."
We ended up spinning up a secondary fleet and bin log replicating from our 5.7 master to the to-be 8.0 master until everything made the switch over.
I was frankly surprised it worked, but it did. It went really smoothly.
Uber's collaboration with Percona is pretty neat. The fact that they've scaled their operations without relying on Oracle's support is a testament to the expertise and vision of their SRE and SWE teams. Respect!
So it's kind of the same difference, no?
how is this done - like a user would have history, payments, etc. are all of them colocated in one cluster ? (which means the sharding is based on userid) ?
is there then a database router service that routes the db query to the correct database ?
Earlier quoted context omitted.
Their focus is prioritized according to what returns maximum value to their shareholders.
beep boop i'm a capitalist robot pretty sure safe travels is critical to maximum value to their shareholders (aka stfu or tell me how this blog post has anything to do with maximize shareholder value https://www.uber.com/en-JO/blog/upgrading-ubers-mysql-fleet/... ... shareholder value is a dumb ass thing to prioritize over human life)
Earlier quoted context omitted.
> I can tell from a mile away that this is written by ChatGPT / Claude, at least partially. Whilst it may smell of ChatGPT/Claude, I think the answer is actually simpler. Look at the authors of the blog, search LinkedIn. They are all based in India, mostly Bangalore. It is therefore more likely to be Indian English. To be absolutely clear, for absolute avoidance of doubt: This is NOT intended a racist comment. Indian…
There's nothing that sticks out to me as obviously Indian English in this blog post. It's almost certainly entirely run through an LLM though.