Am Mittwoch, 2. Januar 2019, 16:01:30 CET schrieb Richard Fuchs:
Internal hash table diffenentelly stores info But even it case of putting timeout to 0 it still grows in synthetic tests. So looks like it will grows alsways because of deletes entries but creates new and so on and so on... So means it decrases "leak" but not fully
Is there some hidden function maybe to drop hast table o some ticky to do this? (we are using oru ow algorinthm that garanties to use same node in case of transaction)
You should be able to set the timeout to zero and the size of the hash table to one (variable `hash_table_size`). That should make the code purge out all entries on every operation, keeping the number of entries minimal.
Hi Richard,
would this information something that is useful to be added to the module README?
Best regards,
Henning