-
@ jb55
2025-04-21 15:58:40
yes this is a good point, the most important and frequently accessed data should be closest to the lowest level cpu caches. Unfortunately most devs are so abstracted away from this idea these days.
This is another reason i love nostrdb’s design. All the nostr data is always hot in cache, and is in a compact binary format for cache efficiency, and even lmdb has an optimial cpu cache structure. The effect is very noticeable.
It also completely changes the way I built notedeck compared to damus ios. No async db calls, since its fast enough to do in realtime at 144fps. No need to keep ui in sync with the db. Each frame always has the latest version. Works offline. Greatly simplifies building nostr apps.
So in other words you are correct, but it’s a very subtle point!