> i don't even understand how khatru based relays are still functioning the excessive amount of threading they use
yeah I know, I've been running Vertex on khatru for few months. Rely uses only 2 go-routines per websocket, one for reading, and one for writing. Then, one goroutine for dealing with client registration, unregistration and requests.
> also, yeah, not to forget, i totally flattened the concurrency of the event store, so, it also is a solution for that, excessive amounts of threads in each query were a component of the resource leak problem i found with khatru/eventstore design
Oh yeah, that part is gone in my design. Users supply their query method and that's it.
In fact, all your cool DB stuff can be used in the rely.
pippellia / Pip the social graph guy
npub176…7vgup
2025-04-04 15:58:49
in reply to nevent1q…29fx
Author Public Key
npub176p7sup477k5738qhxx0hk2n0cty2k5je5uvalzvkvwmw4tltmeqw7vgupPublished at
2025-04-04 15:58:49Event JSON
{
"id": "914a786aad97e5225decaef816abe21086528df38f2b0fc8055676965d60b4d8",
"pubkey": "f683e87035f7ad4f44e0b98cfbd9537e16455a92cd38cefc4cb31db7557f5ef2",
"created_at": 1743782329,
"kind": 1,
"tags": [
[
"e",
"5adbc1b2566f157261dd72748a9f7c81bd2e6a50f8652e4371ab3097d186df43",
"wss://theforest.nostr1.com",
"root",
"f683e87035f7ad4f44e0b98cfbd9537e16455a92cd38cefc4cb31db7557f5ef2"
],
[
"e",
"a040105c4ae7f1575a724a9135c71062e9d093cfb0f138fa2f5d0861dbf779a2",
"wss://theforest.nostr1.com",
"reply"
],
[
"p",
"f683e87035f7ad4f44e0b98cfbd9537e16455a92cd38cefc4cb31db7557f5ef2"
],
[
"p",
"4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f"
],
[
"r",
"wss://mleku.realy.lol/"
],
[
"r",
"wss://relay.damus.io/"
],
[
"r",
"wss://relay.nostr.band/"
],
[
"r",
"wss://relay.primal.net/"
],
[
"r",
"wss://auth.nostr1.com/"
]
],
"content": "\u003e i don't even understand how khatru based relays are still functioning the excessive amount of threading they use \n\nyeah I know, I've been running Vertex on khatru for few months. Rely uses only 2 go-routines per websocket, one for reading, and one for writing. Then, one goroutine for dealing with client registration, unregistration and requests.\n\n\u003e also, yeah, not to forget, i totally flattened the concurrency of the event store, so, it also is a solution for that, excessive amounts of threads in each query were a component of the resource leak problem i found with khatru/eventstore design\n\nOh yeah, that part is gone in my design. Users supply their query method and that's it.\n\nIn fact, all your cool DB stuff can be used in the rely.",
"sig": "60ee3015575e99bd5f9cb118b1c8222dc69462ed61ae38c936314d2fdd673a5b80c858ab89f6ef24a24980d93f36f2facdee41518957767386ef5cf4e30ece4c"
}