bddicken

5 ms·

31.
Add AI to Any App(simeongriggs.dev)
1 points by bddicken 7mo ago|0 comments
32.
by bddicken 7mo ago
epic
33.
Startups Are Sequencing Problems(benhylak.substack.com)
2 points by bddicken 8mo ago|1 comments
34.
by bddicken 8mo ago
Yep. Its a wonderful capability to have for some situations, but for 90% of applications SERIALIZABLE isolation is overkill.
35.
by bddicken 8mo ago
These are still transactions! It's not uncommon for a large % of transactions in an OLTP workload to be only one query without explicit BEGIN / COMMIT; This is called an autocommit transactions or implicit transaction.
36.
by bddicken 8mo ago
Thanks, fixed!
37.
by bddicken 8mo ago
Author here. You're right! I'm fixing now.
38.
by bddicken 8mo ago
I appreciate this feedback, and then you read through it with enough rigor to notice.
39.
by bddicken 8mo ago
Notation is useful. Citations are nice for further reading. But I don't agree more of this makes for a better article!
40.
by bddicken 8mo ago
Author here. Thank you! These visuals are built with js + gsap ( https://gsap.com )
41.
by bddicken 8mo ago
Author here. This is good feedback. The combination of transactions, isolation levels, and MVCC is such a huge undertaking to cover all at once, specially when comparing how it's done across multiple DBs which I attempted here. Always
42.
by bddicken 10mo ago
This is changing soon with Neki. https://www.neki.dev
43.
by bddicken 11mo ago
Love how easy it is to visually correlate schema changes to performance improvements in Insights.
44.
by bddicken 1y ago
Hi, author of the blog here. Benchmarking can be tricky, but I did my best to make this fair and useful to other DB engineers. Ask me anything!
45.
Benchmarking Postgres 17 vs. 18(planetscale.com)
184 points by bddicken 1y ago|64 comments
46.
by bddicken 1y ago
Thank you!
47.
by bddicken 1y ago
Thanks for the feedback! Yeah, I purposefully "simplified" how virtual memory works here so that the focus could be on multitasking and context switching, but agree that isn't totally accurate. I actually had hoped to do a pa
48.
by bddicken 1y ago
Author of the article here. Hope you love it, and I'm hanging around to answer any questions.
49.
by bddicken 1y ago
Still in virtual machines, but ones with local NVMe drives rather than network-attached storage (EBS, Persistent Disk). This means incredible I/O performance. https://planetscale.com/blog/benchmarking-postgres
50.
by bddicken 1y ago
It's real Postgres operated by PlanetScale. You get HA by default, the best performance, query insights, etc. https://planetscale.com/blog/benchmarking-postgres
51.
by bddicken 1y ago
In the database world, serverless/autoscaling pricing is almost always more expensive for real workloads. The % of workloads where it makes sense is small. Ones where 90% of the time there's little small traffic and 10% of the tim
52.
by bddicken 1y ago
Why? Neki is built by the the engineers who have built, maintain, and operate massive-scale Vitess databases.
53.
by bddicken 1y ago
The Postgres team incorporating io_uring into PG 18 is a good example of this: https://pganalyze.com/blog/postgres-18-async-io .
54.
Performance of Threads vs. Processes(medium.com)
1 points by bddicken 1y ago|0 comments
55.
by bddicken 1y ago
This was a great read - thanks!
56.
Benchmarking EC2 Instance Storage(benjdd.com)
1 points by bddicken 1y ago|0 comments
57.
A Graveyard of Hard Drives(benjdd.com)
2 points by bddicken 2y ago|1 comments
58.
by bddicken 2y ago
Hey, Ben here from planetscale. I'm happy to answer any questions about this, or route the appropriate engineer (like the incredible vmg).
59.
by bddicken 2y ago
Or in this case, to spend far more $$ on io2.
60.
by bddicken 2y ago
For writes, yes. But what if your workload is 90% reads?

More ›