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
I still have an OOM issue, even after fixing #529. I'm running in production on low-end hardware (1VCPU, 512 MB ram), but it should have some ram to spare. I'd like to know what's causing this.
Since sleds default cache size is 1gb, maybe that's the problem? Because my server doesn't even have that amount of memory. I'll try using a somewhat decent machine.
Update: after a week of using a machine with 4GB ram, I haven't had any OOMs. The memory usage seems to hang at 448MB total, of which 370 is used by Atomic-Server. I don't think there's a memory leak.
The text was updated successfully, but these errors were encountered:
I still have an OOM issue, even after fixing #529. I'm running in production on low-end hardware (1VCPU, 512 MB ram), but it should have some ram to spare. I'd like to know what's causing this.
I tried running with miri, but it doesn't support Tokio at the moment. I could also try valgrind.
Since sleds default cache size is 1gb, maybe that's the problem? Because my server doesn't even have that amount of memory. I'll try using a somewhat decent machine.
Update: after a week of using a machine with 4GB ram, I haven't had any OOMs. The memory usage seems to hang at 448MB total, of which 370 is used by Atomic-Server. I don't think there's a memory leak.
The text was updated successfully, but these errors were encountered: