Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bw-unified ram usage get's higher every minute until reboot #2843

Closed
1 task done
Tracked by #2480
ChrisSlashNull opened this issue Apr 9, 2023 · 4 comments
Closed
1 task done
Tracked by #2480

bw-unified ram usage get's higher every minute until reboot #2843

ChrisSlashNull opened this issue Apr 9, 2023 · 4 comments
Labels
bug bw-unified-deploy An Issue related to Bitwarden unified deployment

Comments

@ChrisSlashNull
Copy link

ChrisSlashNull commented Apr 9, 2023

Steps To Reproduce

  • Deploy a container with the latest bw-unified beta image and sqlite db
  • Import or create a few login entries

Expected Result

Bitwarden has a constant ram usage.

Actual Result

RAM usage get's higher every minute until a reboot.
On my system the used memory starts at ~400 MB, goes to ~550 MB the first 5 minutes and after 3 days ~1,5 GB and so on.

Screenshots or Videos

3 days after reboot:
image

After reboot:
image

1 Minute after reboot:
image

~10 minutes after reboot
image

~ 60 minutes after reboot
image

Additional Context

No response

Githash Version

decef0e-dirty

Environment Details

OS: Raspberry Pi OS bullseye 64bit
Environment: Docker version 23.0.3
Hardware: Raspberry Pi 4B 8GB

Database Image

sqlite

Issue-Link

#2480

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@ChrisSlashNull ChrisSlashNull added bug bw-unified-deploy An Issue related to Bitwarden unified deployment labels Apr 9, 2023
@kspearrin
Copy link
Member

The ASP.NET applications will garbage collect and release memory if the system needs it. If your server has available memory, the applications may continue to consume. Have you tried restricting the unified container to a fixed amount of memory?

See https://bitwarden.com/help/install-and-deploy-unified-beta/#memory-usage

@ChrisSlashNull
Copy link
Author

The ASP.NET applications will garbage collect and release memory if the system needs it. If your server has available memory, the applications may continue to consume. Have you tried restricting the unified container to a fixed amount of memory?

See https://bitwarden.com/help/install-and-deploy-unified-beta/#memory-usage

Thanks! Didn't know that!
Will I notice a difference in performance when I set a limit at 600mb for example?

@kspearrin
Copy link
Member

You should not, unless you notice crashing because of out of memory errors. In that case, you should raise the limit. 600mb should be more than enough.

@ChrisSlashNull
Copy link
Author

Thanks @kspearrin for explanation!
Sorry for bothering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug bw-unified-deploy An Issue related to Bitwarden unified deployment
Projects
None yet
Development

No branches or pull requests

2 participants