You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that when db-sync is running as a daemon, its memory consumption increases over time - starting at e.g. 300mb, it can get to few gb in several days. There could be some memory leaking...
I'm experiencing this too. Running the docker container on EC2 db-sync eventually maxes out the memory and crashes the box. Setting the container to have a mem_limit of 100mb means it restarts after ~2 hours with the daemon sleep time set to 2 seconds. Block I/O is also high and reaches ~100 G in that time.
Activity
Ojaybee commentedon Sep 29, 2022
I'm experiencing this too. Running the docker container on EC2 db-sync eventually maxes out the memory and crashes the box. Setting the container to have a mem_limit of 100mb means it restarts after ~2 hours with the daemon sleep time set to 2 seconds. Block I/O is also high and reaches ~100 G in that time.
Fix memory leak related to MerginProject object (fixes #78)