search

bropat / eufy-security-ws

Small server wrapper around eufy-security-client library to access it via a WebSocket.
MIT License
177 stars 26 forks source link

[Question]: Memory usage more than doubled since 0.9.4 #170

Closed gmta closed 1 year ago

gmta commented 1 year ago

Ask your question

Previously on 0.9.4, I updated to version 1.3.0 and noticed my Kubernetes cluster was killing the container because it exceed the memory limit of 64MiB I gave it. Upping it to 128MiB was not enough; it seems to peak at about 150MiB after booting for a minute of 2 before finally connecting. Running on ARM64.

Is this behavior to be expected?

yavinmaster commented 1 year ago

I don't know what it was on previous versions, but my Pi is showing 108.5M on 1.3.0. To be honest, I'm just glad the new version fixed Eufy's security changes.

gmta commented 1 year ago

To be honest, I'm just glad the new version fixed Eufy's security changes.

Absolutely, same here. But as a developer I'd like to know when my software would explode in terms of memory usage ;-) I've just performed some additional testing and it seems like a memory limit of 256MiB was not enough, so I've now set it to 512MiB which seems to work consistently.

hanseandersson commented 1 year ago

how do i change the memory limit? My just get "killed" before it finished,,

tmbs1988 commented 1 year ago

how do i change the memory limit? My just get "killed" before it finished,,

+1

gmta commented 1 year ago

how do i change the memory limit?

I'm using K8s pod resource limits. Please open your own issue if you have further questions.

bropat commented 1 year ago

I have removed a resource intensive dependency in version 1.3.1. Please test and let me know.

gmta commented 1 year ago

@bropat Thanks - I've tried 1.3.3 with the old memory limit of 128MiB and it works!