[Support]: Amid memory leak/hog, how much should I limit the container to?

[kingp0dd]

Describe the problem you are having

I've been having a couple of OOM stops due to Frigate consuming a lot of RAM, and it's affecting other containers running in Docker.

Stumbled upon #10921 (comment)

It seems the workaround is to limit the Frigate container's RAM.

How do I know how much RAM it should have? Is it different from the shm calculation that is mentioned in the docs?

Version

0.14.1-f4f3cfa

What browser(s) are you using?

Chrome 88

Frigate config file

.

Relevant Frigate log output

.

Relevant go2rtc log output

.

FFprobe output from your camera

.

Frigate stats

No response

Install method

Docker Compose

docker-compose file or Docker CLI command

.

Object Detector

OpenVino

Network connection

Wired

Camera make and model

Hikvision, Reolink

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

No response

[NickM-27]

yes it is different than SHM. I would suggest just letting frigate run for an hour and then see how much it is using, add 1GB to that

[kingp0dd]

I just realized that Frigate gets killed by Linux OOM when it reaches the resource limit set in Docker compose, which is not ideal as Frigate could miss detections.

I also observed that the RAM usage has increased from a few weeks ago:

From 2.5 GB usage for a few minutes after startup, to 3.5 GB without changing Frigate config nor adding cameras: