Mikhail Mikhailidi retweeted
Today’s deep dive: why Uber moved from Postgres to MySQL.
Really well-written article explaining the problems Uber faced with Postgres and the database internals behind the decision.
uber.com/in/en/blog/postgres…
Mikhail Mikhailidi retweeted
Прием в английском посольстве. Посол пытается через переводчика общаться с подвыпившим советским генералом.
Посол:
-Какую живопись предпочитает генерал?
Генерал:
-эээ...мне нада штобэ были бабы и собаки!
Переводчик:
- генерал предпочитает фламандцев
Mikhail Mikhailidi retweeted
"Worrying about money is silly"
- Person with trust fund who never worked a day in their life
Mikhail Mikhailidi retweeted
Впервые про ИИ агентов, которые всю работу сделают за тебя, но хуёво, я узнал из мультика Вовка в тридевятом царстве.
Mikhail Mikhailidi retweeted
Wife texts husband on a cold winter morning: "Windows frozen, won't open."
Husband texts back: "Gently pour some lukewarm water over it and then gently tap edges with hammer."
Wife texts back 10 minutes later: "Computer really messed up now."
Mikhail Mikhailidi retweeted
Replying to @Ulianalive
Mikhail Mikhailidi retweeted
Replying to @elonmusk
Mikhail Mikhailidi retweeted
Для чего ещё нужен ИИ, если не для такого?
Если бы "Во все тяжкие" сняли в Украине.
Mikhail Mikhailidi retweeted
When to Hire a Computer Performance Engineering Team brendangregg.com/blog/2025-0…
Mikhail Mikhailidi retweeted
I cant stop laughing at how serious he is during it all
This media is unavailable
Mikhail Mikhailidi retweeted
modernDayBlinkerFluid redd.it/1k3i647
Mikhail Mikhailidi retweeted
dotnetDevVillainArc redd.it/1jlrcv2
Mikhail Mikhailidi retweeted
A man walks into a library and asks whether they have a book on Pavlov’s dog and Schrodinger’s cat. The librarian thinks for a moment and says “it rings a bell, but I’m not sure if it’s in or not”
Mikhail Mikhailidi retweeted
Where do OLTP workloads spend most of their time?
In 2008 it was waiting for the CPU.
In 2024 it is waiting for the network.
Applications running on leading databases spend 23%-68% of their time on network communication!
(At least according to "OLTP Through the Looking Glass 16 Years Later" paper from CIDR 25)
Using DPDK (kernel bypass networking) significantly reduces overhead, but is challenging to implement. Using stored procedures reduces, but does not eliminate, the overhead.
The paper also explores the biggest issue with stored procedures - the lack of isolation. They explore several isolation models and show how introducing more isolation also increases the communication overhead.
The only problem with the paper: It is focused on VoltDB, which no one uses, and extrapolates to more popular DBs. Would be interesting to see a PG-centric version of this.






























