When running batch_script_get_history on a Linux machine with processing many scripts the memory consumption is enormous and does not go down. This test showcases this behavior.
When triggering the test with 7000 scripts we see a memory consumption of about 4GB.
Note that you can add a loop to re-trigger the batching to see that the memory does not get freed.
This problem could be reproduced on multiple Linux machine, but not on MacOS.
I opened this Draft PR that contains a test that we used to reproduce this behavior: #89
When running
batch_script_get_historyon a Linux machine with processing many scripts the memory consumption is enormous and does not go down. This test showcases this behavior.When triggering the test with
7000scripts we see a memory consumption of about4GB. Note that you can add a loop to re-trigger the batching to see that the memory does not get freed.This problem could be reproduced on multiple Linux machine, but not on MacOS.
I opened this Draft PR that contains a test that we used to reproduce this behavior: #89