Re^3: Memory utilization and hashes

specifically there can be anywhere from 1 to n answers for each query

Then you can't delete your hash entries as you go, because when a second answer comes of a given query, you no longer have the information from the query available.

Comment on Re^3: Memory utilization and hashes

Replies are listed 'Best First'.
Re^4: Memory utilization and hashes by bfdi533 (Friar) on Jan 17, 2018 at 22:35 UTC
See my last post at the end. I check for a repeat and when I detect it, I delete it and start over. Update: Hmmm, thinking about what you said and what I just said ... Maybe deleting the entry and starting over (though needed to get rid of the last answers) does not really solve my memory issue at all. You might actually be onto something there but I do not know how to fix it, given that it is the case ...	[reply]
Re^5: Memory utilization and hashes by Laurent_R (Canon) on Jan 17, 2018 at 23:48 UTC
In fact, all you need to store in your hash is the queries, there is no reason to store any answer in the hash, since you can process it immediately and print it. This may help, but I'm not sure, though, that this is sufficient to reduce your memory footprint to an acceptable level (it depends on your data profile).	[reply]