pr on Nostr: number of cores depends on how many users you want to service at the same time and if ...
number of cores depends on how many users you want to service at the same time and if you want to do media caching. try it with at least 4 cores. as for memory, with 16GB RAM it should work fine, 32GB is what i usually suggest as it will have more opportunity to use disk I/O cache and since you probably have some other processes running on the server. for storage, after 6 months and 125mil events, our database is around 330GB. but i could prune older events and reduce storage requirements if you dont want to archive everything forever.
Published at
2023-08-03 10:30:09Event JSON
{
"id": "c54e184103ce873e23517ecdc3a38cdd24f76d70929d45a9f1b5f1481d92b62a",
"pubkey": "dd9b989dfe5e0840a92538f3e9f84f674e5f17ab05932efbacb4d8e6c905f302",
"created_at": 1691058609,
"kind": 1,
"tags": [
[
"e",
"d88b2659634db0f49754d3049b30c3688f9f269e2f5f25ce7fb0659c9535e333",
"",
"reply"
],
[
"p",
"9fec72d579baaa772af9e71e638b529215721ace6e0f8320725ecbf9f77f85b1"
]
],
"content": "number of cores depends on how many users you want to service at the same time and if you want to do media caching. try it with at least 4 cores. as for memory, with 16GB RAM it should work fine, 32GB is what i usually suggest as it will have more opportunity to use disk I/O cache and since you probably have some other processes running on the server. for storage, after 6 months and 125mil events, our database is around 330GB. but i could prune older events and reduce storage requirements if you dont want to archive everything forever.",
"sig": "e14b2bcdcd53017696f92e933b8d4d3f8c31680d310feb9828bfe75f862316683d49bbaa25cf8f05860f1895c154b96ffc4b50a403fb371b38050c7ee616b822"
}
