Can they change the 'lasts' parameter so that things don't expire as quickly?
Another idea.
To be more sophisticated, instead of killing fnids, could first
; replace them with fns that tell the server it's harvesting too
; aggressively if they start to get called. But the right thing to
; do is estimate what the max no of fnids can be and set the harvest
; limit there-- beyond that the only solution is to buy more memory.
(def harvest-fnids ((o n 50000)) ; was 20000
Can they change that number? Maybe that would help.
Another idea. Could you change it so that when they are harvested the functions are serialized to disk (maybe temporarily), and make fns a function or something so if it had been removed from memory it could be deserialized? It wouldn't need to be a serialization solution that would work for arbitrary closures, just something that would work for those cases, like timed-aform or whatever.
I have barely ever tried to use Lisp and I don't know much about this system so this may not make any sense.
Another idea. Use one of the Hacker News clones that people have built over the years that doesn't have this problem.
Can they change the 'lasts' parameter so that things don't expire as quickly?
Another idea.
Can they change that number? Maybe that would help.Another idea. Could you change it so that when they are harvested the functions are serialized to disk (maybe temporarily), and make fns a function or something so if it had been removed from memory it could be deserialized? It wouldn't need to be a serialization solution that would work for arbitrary closures, just something that would work for those cases, like timed-aform or whatever.
I have barely ever tried to use Lisp and I don't know much about this system so this may not make any sense.
Another idea. Use one of the Hacker News clones that people have built over the years that doesn't have this problem.