Event JSON
{
"id": "b622898f8f17dc6ba2b021a58217786c36925111543bc03d0dcf23c288c309fc",
"pubkey": "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
"created_at": 1748194686,
"kind": 1,
"tags": [
[
"e",
"79637d8f3a47d79f05afdd482c284a909b98f4b9735f4ec2f50bf79d4aa00834",
"",
"root"
],
[
"e",
"5ed451aff2cf362d2c7876d4eeb9ef73b6c81407a821d6d36edc6209b335b380",
"wss://theforest.nostr1.com/",
"reply",
"7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e"
],
[
"p",
"4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"wss://theforest.nostr1.com/"
],
[
"p",
"846ebf79a0a8813274ec9727490621ad423f16a3e474d7fd66e6a98bfe4e39a4",
"wss://theforest.nostr1.com/"
],
[
"p",
"70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9",
"wss://nostr.wine/"
],
[
"p",
"7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e",
"wss://bevo.nostr1.com/"
],
[
"p",
"036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
"wss://relay.nostr.band/"
],
[
"p",
"fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1",
"wss://theforest.nostr1.com/"
],
[
"p",
"52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd",
"wss://hist.nostr.land"
],
[
"p",
"fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1",
"wss://theforest.nostr1.com/"
],
[
"p",
"fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1",
"wss://theforest.nostr1.com/"
]
],
"content": "Yeah so 8k open connections, not 8k in use fair enough. Yeah my concern is we need way more than a single instance and (I hope) way more than 8k active connections to support a product like Alexandria assuming we get anywhere close the reach were aiming for. I just want the software to exist for the time we DO need it. Like I said in my argument before. In just about any other software deployment, the software exists to scale, if needed, but not implemented _until_ needed. What happens when we do need it, and it doesn't exist? \n\nBeyond that my concern, and I made this number up, something like a latency log scale showing some sort of \"rolloff\" - when load gets high enough to cause latency to creep to the point the service becomes interrupted or noticeable to the end user. ",
"sig": "1ebdd6dc483fb632c0d5d8c87e456518ae140b4e0ab2b67b6890923caa99c0a6e0e5832b39e9bc7b70a25130bf2d9c03a297cc112e7906822f8f5080b607423b"
}