Describe the bughybrid-echidna crashes my machine since with each new iteration (i.e., echidna campaign) the memory usage grows rapidly. I could increase the amount of RAM or swap available since I'm running on a VM in the cloud but it's hard to predict what the total usage will be.
This severly limits usability of optik to me since I can only run with very low --max-iters and that in turn limits --seq-len of echidna campaigns.
I hope there might be some low-hanging fruit where some of the memory contents can be discarded or dumped on the disk.
Additional context:
Ubuntu 22.04.1 LTS on a Google Cloud instance
Describe the bug
hybrid-echidna
crashes my machine since with each new iteration (i.e., echidna campaign) the memory usage grows rapidly. I could increase the amount of RAM or swap available since I'm running on a VM in the cloud but it's hard to predict what the total usage will be.This severly limits usability of optik to me since I can only run with very low
--max-iters
and that in turn limits--seq-len
of echidna campaigns.I hope there might be some low-hanging fruit where some of the memory contents can be discarded or dumped on the disk.
Additional context: Ubuntu 22.04.1 LTS on a Google Cloud instance
hybrid-echidna logs: echidna.logs.issue.txt
Google Cloud memory usage chart: (Note: the final plateau is probably not really a plateau because the swap was being used instead of RAM)