Yuki Kishimoto on Nostr: It's intentional. Using in-memory indexes remove some work to me. But in the long ...
It's intentional. Using in-memory indexes remove some work to me. But in the long term it will probably be replaced with DB-native indexes.
I not done tests/benches with native indexes yet, but indexeddb (the db for the browser), in general, it's slow... so in-memory indexes help a bit.
Published at
2024-05-07 06:34:59Event JSON
{
"id": "347839a674ac650ba9c309c34769466c03863def5e6947a473dc71a925140d6c",
"pubkey": "68d81165918100b7da43fc28f7d1fc12554466e1115886b9e7bb326f65ec4272",
"created_at": 1715063699,
"kind": 1,
"tags": [
[
"e",
"fda94190ca1dd52a0a37447a2f0f2fb8a1c34bf7cd6dfced6a230180bf009ab4",
"",
"root"
],
[
"p",
"68d81165918100b7da43fc28f7d1fc12554466e1115886b9e7bb326f65ec4272"
],
[
"p",
"2cb30c36438bad4a2a5107bc98f5cebe6a0229b0554d8cfbd1c99aa3cc7ecec1"
]
],
"content": "It's intentional. Using in-memory indexes remove some work to me. But in the long term it will probably be replaced with DB-native indexes.\n\nI not done tests/benches with native indexes yet, but indexeddb (the db for the browser), in general, it's slow... so in-memory indexes help a bit.",
"sig": "34f3201d10a8f3c2f70480339debd5627bbc6f93e73dbe5cc07c346f26974888c1b2e5d8e6cc5fe79012086da2d056a0a1f749a89e2ddcde52dd2729fae7acdf"
}
