throwusawayus

lol regarding smart smoke detectors

firstalert acquired luma, which had acquired birdi, which was kickstarter campaign smart smoke thing, which shipped nothing to most of kickstarter backers

some m&a execs clearly did not have good vaporware detector there!!

ok. json columns were put in eight years ago

think of big features added to oracles Mysql in past two years. Thats ten releases: eight most recent 8.0.xx, and 8.1 and 8.2.

what are they? are you using any? does it really not worry you at all?

youtube migrated away from vitess several years ago

Mysql product is circling drain under oracles direction anymore. New 8.x “innovation” releases lack any important features. even Mariadb is out executing oracle despite being broke!

Mysql community is in bad shape too. Official slack channel is avalanche of lazy newbie questions. Official linkedin group is endless spew of “learn sql cheat sheet”

Sad. It’s done for. community may still be “enormous” but that is bad thing when its communication channels overrun by sub-bootcamp-level devs

innodb supports cross-schema foreign keys, there’s no limitation to tables in a single database

can be terrible in mysql 8 though due to metadata locks now extending across foreign key boundaries. this means alter in one schema can block things in other schema if foreign key across databases

speaking of, am surprised that blog post author doesnt discuss the new mysql 8 metadata locking behavior, is new major problem with mysql foreign keys!

only oracle knows. and they don’t share answer yet, on this site or any other

only public news so far is extremely brief twitter mention of future switch to separate LTS releases from feature releases

big picture, hard to see what would motivate them to major re-invest in current mysql product model! amazon, planetscale, and co all profit off of oracle’s mysql server development efforts. and oracle does not get anything in return

assume this why more and more mysql dev efforts go to saas-only product like “mysql heatwave”!

you are spending time creating multi-year linked list of hn comments every single time a website you dislike and dont use goes down

i am “failing to address main issue of github’s downtime history”? indeed sure i am not addressing this, because it is not my care to address! why care when website i dont use and dont like goes down? not my problem!

do you see anyone else on entire hn creating redundant toplevel comments that then link to previous comment on same topic, spanning hundreds of comments across multiple years, all to post told-you-so to some random other commenters from 2-3 years ago? no one else do this, is deranged!

i pointed out no one in THIS THREAD said anything about “all in on github” and you replied linking to different thread from TWO YEARS AGO. deranged!

who else posts i-told-you-so’s hundreds of times for two years shouting to void? is madness!

>> it is more 'deranged' to believe that GitHub has gotten any more reliable after Microsoft acquired it.

ok? and who in THIS THREAD is saying anything remotely like that?

>> You can continue to use GitHub's services, but don't complain when something from GitHub goes down again

i dont use githubs services, where did i say i do?

i have not conplained about github going down

who are you responding to??!?? comments makes no sense, derangement!!!

so, because two people said they go all in on github on an hn thread TWO YEARS AGO , you feel the need to post public i-told-you-so hundreds of times ???!???

i am amazed @dang is ok with that, it seem completely deranged man, borderline harassment

why always repeatedly write the same comment about not going “all in on github” in these threads? what is goal of writing this hundred+ times?

https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...

i dislike github quite alot but this does not achieve anything. no one else is saying to go all in on github so what is this even reply to?

have done both. meth is a strong drug but its experience is absolutely not “profound” at all

why do you keep making comments like this about meth in this thread?

better comparison, LSD and shrooms are very profound, but in a different way than E, think like introspective -vs- social

even better comparison is 2ct7, felt like a nice balanced combination of mdma and lsd, profound but not overwhelmingly

i strongly dislike planetscale and even i think this is not a useful or fair comparison .. sqlite works with local files, much simpler, no network latency, no HA

tracking access time (every read) is huge performance bottleneck. especially if reliably persisting this

same reason why filesystems are often mounted with noatime attribute !

article title is misleading! it is about planetscale only, not mysql in general. borderline click bait

also posted by a former github person. not sure if poster is author or works at planetscale but a lot of ex github engg are there

maybe helps that project co creator is famous photographer https://en.m.wikipedia.org/wiki/Noah_Kalina

heard zuckerberg booked him as wedding photographer (for real)

more impressive that they had to assassinate someone three times! who was victim, Grigori Rasputin??

i was talking about managed sql databases

your first two examples are nosql. third example charges by data size processed, not by rows!

rows is weird metric since some tables have tiny rows, some have huge

you just are not understanding my point, that does not mean i am acting in bad faith! jeez

i originally said pricing for other managed sql dbs, not specifically “serverless” ones. we both know that is just a marketing term anyway

with ACUs the point is you configure min and max, and your cluster scales up/down based on a cpu utilization threshold. so, sure reading from memory uses cpu cycles — but a large cached read is incredibly unlikely to bump you over a scaling threshold which affects your bill, unless you’re doing some huge heavy sort operations

another key point is aurora serverless v2 does not scale down to 0 acu. you are always paying a predictable small amount for your base cpu and ram. minor increases in cpu usage literally do not impact your bill at all, which is why i do not believe your argument makes sense regarding cached reads.

edit to add: the reason this matters for monetary cost of ELT/ETL is it often involves very large reads. if your jobs only extract recent/changed data, this will very likely be in buffer pool, and cost way less with io pricing than with your row based pricing. clear?

aurora serverless pricing is not based on cpu cycles. this is just not how ACUs actually work or scale or are priced, at all man

anyway i gather the answer to my question is that no, there are no other examples of managed sql dbs that bill the way you do. my complaint is this is inherently not transparent because it violates user expectations. users try comparing to io based provders and fail to understand the pricing math comparison (on io pricing 1 read = many rows) or caching implications (on io pricing, cached rows dont count as io)

as for denigrating rds, look to your ceos past hn comments. i would link to it, but last time i did that i got flagged, despite it being a recent thread that i was directly participating in

what other managed sql DBs charge based on rows read, regardless of whether they are on-disk or in-memory? honest question. i am familiar with a number of managed mysql and postgres products, and none of them bill this way that i have ever seen

and for the record, despite planetscale staffers repeatedly denigrating rds (your competitor) on hn, aurora’s patch set is not “minimal”

i do think vitess is cool for what its worth. i just think your managed db product has bananas billing and also is horrendously over hyped, and your ceo’s responses to criticism are very reminiscant of theranos or wework’s responses to same

wondering, any culture clash aspect? (did you move to other country for job)

this is tough in US and Canada in my experience. manager has to tread lightly too, or else manager gets fired for sounding xenophobic

that screenshot tweet is DDG founder/ceo, so not just “some employee”

agree that official announcement would be better though

if you think purpose of my comments is to “throw us off our vision and mission” you are mistaken

this is your response to valid criticism of your pricing model and functionality? as ceo? really?

tz setup is done with executing a single script. not surprising they could fix quickly. bigger surprise is they forgot to do this before youre support request. generally this is table stakes for managed DB

this is fourth day in a row of planetscale ads^H^H^H blog posts being on hn front page. as i mentioned on yesterdays thread, innodb_rows_read is known to be buggy. regardless, by design it includes cached rows. terrible thing to base billing on. real cloud providers base it on i/o instead since this is more reasonable metric of "use"

planetscale's fork of mysql-server adds only a single commit, which exposes rows_read in an extra place. this from company that keeps talking about "building a database" https://github.com/planetscale/mysql-server

worse, theyre pricing is based on innodb_rows_read, even includes cached rows.. so every single ELT job costs $$$ based on how many rows you have, even if all in buffer pool cache already

double-worse, innodb_rows_read known to be buggy! example https://jfg-mysql.blogspot.com/2022/03/rows-examined-not-tru... -- this bug is in customer's favor but what if other bugs are not?!

> I suspect the intention is something more like IPFS (https://ipfs.io), built on some distributed data structure like a DHT.

the company's products are all built on top of sharded mysql .. unless they plan to throw away everything they have done so far, i do not think these assumptions are correct!

creator of prefect was an early major airflow committer. anyone know what motivated the substantial rewrite of prefect? i had assumed original version of prefect was already supposed to fix some design issues in airflow?

bunch of principles here are specific to using managed 3rd-party database, rather than self host // on-prem

meanwhile.. lots of apocalyptic posts lately about how vc funding will dry up since public tech stocks have crashed

so how safe is it to have your business completely rely on a managed database startup, instead of self host or using a major cloud provider's direct offering? may be unwise these days methinks

oh i see now thanks .. was not obvious that these images were clickable or had alt-text with name & title