[Support]: how big is too big for shm_size?

[ReticentRobot]

Describe the problem you are having

I just got started with frigate (never used docker before and not much of a linux person, so that was a bit of a learning process so far) and now I'm setting up the docker compose yaml file. I'm looking at shm_size and trying to figure out what I should go with. I currently only have 2 cameras (reolink doorbells) to use, but will be replacing 5 other Nest cameras with something I can get hold of a local stream soon too. The reolink doorbells have a resolution of 2560*1920 - which comes out to 63.54mb each. If I assume my replacement cameras will all be of similar resolution, would I put shm_size at 445mb? Is that too large, or is there no upper limit I should be concerned about. If it matters, I'll be running it on bare-metal Ubuntu with docker compose on an i7-8700, 48gb ram, 512gb SSD, and a 16tb 7200rpm hdd for recording storage. I have both a USB coral and an m.2 PCIe one installed. Thanks for any help!! I'm guessing on the version below since I haven't installed anything yet, pulling it from the yaml file off the installation page.

Version

3.9

Frigate config file

Do not yet have

Relevant log output

Do not yet have

FFprobe output from your camera

N/A

Frigate stats

No response

Operating system

Debian

Install method

Docker Compose

Coral version

USB

Network connection

Wired

Camera make and model

reolink doorbell

Any other information that may be helpful

No response

[NickM-27]

That number is fine. Technically the space isn't used unless frigate needs it but it's best to not go crazy in case something goes wrong. 512 MB seems like a safe upper bound.

[ReticentRobot]

Nice! Thank you for such a quick reply!!