Just finished some initial query support in #nostrdb.
looks like the query performance for {kind: n, limit: 500} over 1 million records is about 1.6 milliseconds.
So if you ran this query every frame, you would still hit 625fps.
Discussion
Your message is garnering a lot of interest.
Added to the https://nostraco.in/hot feed
Can anyone explain nostrdb to me like I'm retarded ,because that is infact a reality.
Not to deep into it, but nostrdb is the local database running on your phone that’ll serve you the events you’re interested in, when using the Damus app. Making it as performant as possible will increase the user experience, since the reaction time of your phone will be faster, making it feel more seamless.
Given so many nostr apps it would be cool to have a way to communicate with an on-device nostr server instead of all individually getting the same the information from the network repeatedly.
I think it can only be locally used by Damus, so no other app can access it as far as I understand.
nostrdb is built on lmdb which allows concurrent access. You could have multiple processes reading from and writing to the same database. Probably not on phones, but desktop apps could do this.
Probably not on phones because apps are pretty insulated from each other. But it would be awesome though
