Re:Leaks in Persistent Memory
by h2odragon on Tuesday September 24, 2019 @11:03AM
(#21060931)
Reasonable explanation of and suggested solution for the problem. Think I'd say "screw the housekeeping" and design for a garbage collector to periodically sweep the persistent store, likely as an independent process needing no data not already in that store. Then you're covered for the cases the transaction manager still drops.
[ Parent
| on HN ]
That's part of what fsck would do for filesystems
That's essentially the process I used for an application which had a hierarchical graph-like database structure. The naive implementation would check if a node could be pruned (i.e. if it had no connections) every time a connection was removed. But it turned out it was a lot more performant to just periodically sweep for nodes with no connections like once a day.