-
Notifications
You must be signed in to change notification settings - Fork 187
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
containers memory usage #148
Comments
Hello @j2l elasticsearch is responsible for full-text search. If you don't need it, you can turn it off. For our application, the minimum requirements are 6GB of ram and a swap file, if you limit memory consumption, we cannot guarantee the stable operation of all services. |
Thanks @Carazyda |
How many active users do you currently have on the portal? Or is it consumption immediately after installation? What is your host OS? |
Sorry, but v12.0 is on testing now. Release version is 11.6. Please try with it. |
Sorry, forgot to say, the release install didn't work at all for me. |
Can you point out what specific problems you are facing with installing version 11.6? |
Most of these issues are old and closed. Please describe your problems again in new issues. Or wait for the 12.0 release, which is coming soon. |
Hello @wlfcss most of used memory is reserved for the elasticsearch for indexing full-text search in documents and mail. What exactly is your problem? Memory runs out and application crashes? |
The 3 more demanding containers on my home VPS are onlyoffice:
![image](https://user-images.githubusercontent.com/65325/162913957-f87470e0-98d5-4dde-b704-7afa002805f6.png)
I'm not sure I need Elastic Search.
![image](https://user-images.githubusercontent.com/65325/162927229-1dad079e-2388-4951-bf0a-93a60ebbe9c9.png)
When I shut down Elastic Search container, I got many other onlyoffice containers eating the memory:
In my docker-compose.yml, I added
on documents and community containers but it looks like everything is trying to eat all the memory none the less.
Any idea how to limit though voracious beasts?
😄
The text was updated successfully, but these errors were encountered: