Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
throwusawayus
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
throwusawayus
5y ago
"8 people are working on R2Devops!" but none have names or facial features ? https://r2devops.io/team sorry for mean feedback, but is weird after seeing "transparency" as top value!
32.
▲
by
throwusawayus
5y ago
author invented xml. while i haven't any love for xml i assume he is on solid technical footing and just worded poorly ?
33.
▲
by
throwusawayus
5y ago
i was not even the commenter who said they were "pathetic", sheesh now you are attributing others' comments to me! i have posted many correct technical details in various subthreads of this post. i don't care if you beli
34.
▲
by
throwusawayus
5y ago
innodb global lock architecture has improved greatly since 5.1. ancient bug report from harrison is not indicative of problem here. what you think, facebook has unsolvable database cpu pileups for 12 years straight? harrison would not have
35.
▲
by
throwusawayus
5y ago
i have personally been on teams that solved this problem and worked on this problem. across multiple companies. with larger DB size than github's. if you think Percona and Pythian implement sharding solutions, you are deeply mistaken
36.
▲
by
throwusawayus
5y ago
I do in fact know who else would have had similar problems, directly from personal experience and experience of coworkers and friends. large-scale mysql community is fairly insular, lots of talent rotation between the large scale companies
37.
▲
by
throwusawayus
5y ago
so i would agree when talking about comments like "i could code twitter in a weekend! why so many engineers there!" but this is different. github is a 14 year old company, with annual revenue in the hundreds of millions USD I lite
38.
▲
by
throwusawayus
5y ago
why do you blindly assume the person you are replying to has not worked at scale? hundreds of engineers have worked deeply on sharded mysql at massive scale, many of us comment on HN!
39.
▲
by
throwusawayus
5y ago
too idealistic. invariably some team (or usually many teams) don't properly gate some critical-path logic, they depend on some functional partition always being online and then boom much larger blast radius than intended then they fix
40.
▲
by
throwusawayus
5y ago
yeah but half the risk is on the application side, completely independent of planetscale! not all applications can handle some schema change occurring and then suddenly reversing. someone may get fired just trying to win a shirt also their
41.
▲
by
throwusawayus
5y ago
i did so because it is directly relevant to this topic! the person who for many years was directly responsible for github's databases, and later their overall infrastructure, recently made a horrendously inaccurate statement about th
42.
▲
by
throwusawayus
5y ago
"We are giving away limited-edition, retro Rewind t-shirts to the first 100 people that successfully revert a schema change." they are encouraging people to record videos of making schema changes and reverting them, in order to wi
43.
▲
by
throwusawayus
5y ago
> But then, you lose data; all the data you've accumulated since the migration completed; or some data you've deleted will suddenly reappear. this is not correct, for example pt-online-schema-change has long had a --reverse-tri
44.
▲
by
throwusawayus
5y ago
he accused me of making a gross simplification. i responded, perhaps unkindly. but at no point have i "harassed" him. github's outages have made my life difficult. planetscale's pricing scheme has also burned me. i am no
45.
▲
by
throwusawayus
5y ago
> offtopic argument which should have been pursued only in the original context I would have gladly had that discussion in the original context! but he did not reply to me there, nor to any of the other 6 people who replied to that horre
46.
▲
by
throwusawayus
5y ago
i did not dig through his comment history. i was directly participating in that thread i quoted! and it was a recent thread. please check it again. i agree though my comment could have been nicer. apologies. as to adding nothing to the thre
47.
▲
by
throwusawayus
5y ago
this is my exact point: they hired the former head of GH infrastructure - literally the person directly responsible for all this at github for years - and made him their ceo github should have sharded years ago , every other large mysql
48.
▲
by
throwusawayus
5y ago
i'm not suggesting that these departures are the cause of github's issue. rather, i'm saying i don't understand why such a large group from github was hired by planetscale if they did not have experience successfully sha
49.
▲
by
throwusawayus
5y ago
galera is not a solution for scaling out writes, full stop galera has lower max writes/sec than a traditional async single master because it's a cluster. the other members of the cluster need to ack the writes, and all members are
50.
▲
by
throwusawayus
5y ago
yes i know, the fact that this is a small blurb at the bottom of the article (which is largely about functional partitioning) exactly proves my point
51.
▲
by
throwusawayus
5y ago
from that article it sounds like they are mostly doing "functional partitioning" (moving tables off to other db primary/replica clusters) rather than true sharding (splitting up tables by ranges of data) functional partitioni
52.
▲
by
throwusawayus
5y ago
it's profoundly strange that github has not properly sharded yet. essentially all large social networks are or have used sharded mysql successfully, this is not rocket science livejournal, facebook, twitter, linkedin, tumblr, pinterest
53.
▲
by
throwusawayus
5y ago
i agree that is disturbing but it is not what i was referring to, sorry I meant excess old people - age demographics - not excess men. based on projections china's population peaked ~last year. it is a shrinking population from here, a
54.
▲
by
throwusawayus
5y ago
at all levels ? there must be limits to this approach right ??? otherwise this way of thinking gets terrifying fast and rapidly descends into conspiracy theory land example: "need to find a socially-acceptable solution to a demographic
55.
▲
by
throwusawayus
5y ago
that's fair. i am just raising an eyebrow to github's apparent lack of sharding, as described in their incident reports -- while these engineers all left to join a db company that focuses specifically on sharding -- it seems like
56.
▲
by
throwusawayus
5y ago
maybe i shouldn't have mentioned it, i don't want to name names and have this to come off as an off-topic attack subthread about a different company, sorry! it's a db company that has raised a lot of money and is mentioned on
57.
▲
by
throwusawayus
5y ago
i've noticed this too .. the real head-scratcher is how a solid chunk of github's db & infra folks left to join a database startup, one of them even becoming its ceo!! if they had made github db/infra super-stable before
58.
▲
by
throwusawayus
5y ago
> Its The United States of America not United States of America Not the same situation at all! With the US, "the" is officially part of the name of the country, used in the very first sentence of the US Constitution. And even
59.
▲
by
throwusawayus
5y ago
Anecdotal, but I have been told this long before this war: "There's no 'The' before Ukraine, and also there's no 't' at the end of 'borsch'" Why assume this is Western virtue signaling? The
60.
▲
by
throwusawayus
5y ago
> I don't know what more you could be looking for as to what "rows read" means than `innodb_rows_read` On the contrary, this is completely unclear because the mysql manual doesn't even give a clear explanation at all!
More ›