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
Describe the bug
This is related to: #2963
Even after setting GO garbage collection, we still observe daserver hitting OOM within short amount of time.
It's unclear why daserver requires so much GB of memory within a few minutes.
To Reproduce
Adjust resource limit for daserver
Specify GOGC=80 and GOMEMLIMIT=(90% of memory limit)
Run the daserver
Repeat steps 1-3 with different resource limits
In a matter of minutes, the daserver memory usage surges and straddles the memory limit line
Expected behavior
As daserver is basically just a storage and signing service, I would not have expected it to require this amount of storage.
So maybe some unnecessary caching is happening under the hood.
Additional context
Here is the log from the point where the final surge occurs in the screenshot. daserver-log.txt
The text was updated successfully, but these errors were encountered:
Describe the bug
This is related to: #2963
Even after setting GO garbage collection, we still observe
daserver
hitting OOM within short amount of time.It's unclear why
daserver
requires so much GB of memory within a few minutes.To Reproduce
daserver
GOGC=80
andGOMEMLIMIT=(90% of memory limit)
daserver
In a matter of minutes, the

daserver
memory usage surges and straddles the memory limit lineExpected behavior
As
daserver
is basically just a storage and signing service, I would not have expected it to require this amount of storage.So maybe some unnecessary caching is happening under the hood.
Additional context
Here is the log from the point where the final surge occurs in the screenshot.
daserver-log.txt
The text was updated successfully, but these errors were encountered: