"I was considering using #LMDB (which uses mmap) in a NodeJS server but page faults would block the event loop stopping it from processing requests. Benchmarks can be misleading."

https://xcancel.com/Amr__Elmohamady/status/2014672445244895449#m

Pretty sure that pagefault handling is still at least an order of magnitude faster than anything a Node.JS server can process. People always worrying about the wrong things in their code...

"thanks to Blade Battery 2.0, its battery can be charged from 10% to 97% in a mere 9 minutes and 8 seconds. When asked why it charges to 97% instead of 100%, BYD CEO Wang Chuanfu quipped, “You always need to leave a little room for regenerative braking!”"

I've always thought they should build EVs with a Jacob's Ladder sticking out the back, to bleed off excess energy when the battery is full while regenerative braking. It would look awesome, and discourage tailgating.

https://carnewschina.com/2026/03/05/the-worlds-longest-range-ev-launched-denza-z9-gt-offers-1036km-and-9-minute-full-charge-from-39100-usd/

"lmdb/lmdb-win32-arm64
6 days ago — Platform specific binary for lmdb on win32 OS with arm64 architecture. Latest version: 3.5.2, last published: 4 days ago."

Yeah, no. #LMDB is an embedded DB library, intentionally kept under 64KB, so that it can be built statically and *embedded* into each app that uses it. It makes a difference whether you build it for 32bit or 64bit apps, and 32bit or 64bit DBs. You can't just build it once and call it "the platform/system LMDB". Stop doing this.

This is why we don't have nice things. People all across the internet ask for help and take and take without even a single thought of giving back.

When you post a question online, always post the actual answer too if you find it.