Open AmazingDreams opened 10 years ago
All right; Never noticed, processing all blocks at once (Memory limit here is 128M) Maybe a few unsets are needed although these should be implicit.
I figure it is a better idea to separate the indexing from the ROT. Therefore I have started working on a library (which I want to use anyway) which does exactly that. Provide a backend for reading the chain but leave it up to the user to decide where and how he is going to store the information.
It will probably be more bloated than a procedural approach, but the flexibility is a big plus.
Perfect ! The index just allows fast navigation and future "duties" may require speed in different directions. Beyond ROT it is also a building block for wallet services e.a.
When processing a lot of blocks at once, memory is leaking somewhere.