After the devastating earthquakes in Venezuela, rescuers pulled an 18-day-old baby alive from the rubble of a collapsed building. The baby was handed back to his father, and about 90 minutes later, crews also rescued the child’s mother.
An interesting thing is going, here.
In the cat world, being the one that grooms the other one means they're the boss.
In the bunny world it's the other way round: the one being groomed is the boss.
So these two are both thinking they're the boss.
parents: "move out"
girlfriend: “quit being such a loser”
boss: "work harder"
claude: "uber for dogs (the dogs are the drivers) is a great idea, you should absolutely pursue it"
supervision just hit 40,000 GitHub stars!
it now powers over 6.5k open-source computer vision projects, including all my demos like basketball AI
link: https://t.co/xXMRaS4ejS
🩸JUST IN: Over $635 BILLION WIPED OUT from the crypto market in less than a month.
+$500M in crypto liquidations hit in the last 1hr, long positions accounting for $450M.
in 2000, @saylor was the laughing stock of wall street after losing $6B of investors money.
but he didn’t quit.
he spent the next 26 years of his life retard maxxing and found a new way to run it back and achieve an even bigger loss of investors money.
inspirational 💯
Fun fact: Redis does not just rely on the standard operating system memory allocator. Even though it's written in C, it overrides the native `malloc` implementation with highly optimized third-party memory allocators like `jemalloc` (by Facebook) or `tcmalloc` (by Google) to achieve efficiency and low-fragmentation performance.
I firmly believe that understanding theory is fine, but things become interesting when you sit down to implement it. This is where you find gaps in your understanding and understand the nuances. and hence...
Today, we dive into the source code of Redis to look at how and why Redis overrides the default `malloc` implementation.
This is the 18th video in the Redis Internals series. Like always, we keep our focus on execution and not just theory, looking closely at how an in-memory database handles massive amounts of small object allocations and deallocations without crumbling under memory fragmentation.
In the video, I talk about memory pages, how native allocators interact with the OS, and the classic problem of fragmented memory. We also look directly at the Redis source code and see how they wrapped malloc with zmalloc to abstract out the implementation.
By the way, 18 videos are now live:
1. Why Single-Threaded Redis Is Fast
2. Writing a TCP Echo Server
3. Wire Protocols
4. Implementing RESP
5. Implementing PING
6. Understanding Event Loops
7. Implementing Event Loops
8. Implementing GET, SET, and TTL
9. Implementing DEL, EXPIRE, and Cleanup
10. Evictions and Implementing first-eviction
11. Implementing Command Pipelining
12. Implementing AOF Persistence
13. Objects, Encodings, and Implementing INCR
14. Implementing INFO and allkeys-random Eviction
15. The Approximated LRU Algorithm
16. Implementing the Approx LRU Algorithm
17. How Redis Caps Its Memory Usage
18. How and Why Redis Overrides Malloc
If you have ever wondered how scale-critical systems avoid performance degradation over time and handle advanced manual memory management with custom concurrency and defragmentation controls, this deep dive is for you.
Hope this helps you better understand database internals and spark that engineering curiosity.
Give it a watch.
NEW: Amazon has reportedly scrapped its internal AI leaderboard as costs soared, with a senior executive telling staff: “don’t use AI just for the sake of using AI.”