#orly #devstr #progressreport

since adding a spider to collect various directory events of the social graph of designated relay owners, the relay's memory utilization has gone up so much that it's using around 11gb of memory at peak and this is blowing up and causing the kernel OOM killer to keep on restarting the relay on wss://realy.mleku.dev

i've gotta refactor the spider so it is more memory efficient. even just necking it down to a single thread it's still burning so much memory.

aargh. the LLM coding agent wasn't successful in improving the situation either, i need to refactor this spider code so it disposes of memory more efficiently.