![]() Using those file data in sqlite table would reduce file context data to the constant value. Current solution, as observed in this thread is prone to a large memory working set. I would rather like to have a queue of those files in sqlite table, with statuses as “new”, “need hash”, “during hash”, “hash ok” or similar. Currently it looks as a sequential solution (I understand the channel for pumping has no means of synchronization with the channel for hashing - hence the memory hogging).
0 Comments
Leave a Reply. |