Skip to content
This repository has been archived by the owner on Apr 12, 2022. It is now read-only.

Should we recommend limiting memory if it affects VFS cache? #122

Closed
ninaspitfire opened this issue Sep 27, 2017 · 2 comments
Closed

Should we recommend limiting memory if it affects VFS cache? #122

ninaspitfire opened this issue Sep 27, 2017 · 2 comments
Assignees
Labels

Comments

@ninaspitfire
Copy link
Contributor

In our documentation, we suggest setting a memory limit for Elasticsearch containers. However, Docker uses the memory.limit_in_bytes property of the kernel Memory Resource Controller to achieve this, which also appears to limit the amount of file cache that the process has access to.

File cache can be beneficial to Elasticsearch performance, so perhaps we should adjust our recommendation. We could either include a note about the limiting effect on file cache or remove the recommendation altogether.

@ninaspitfire ninaspitfire changed the title Should we recommend limiting memory if it effects VFS cache? Should we recommend limiting memory if it affects VFS cache? Sep 27, 2017
@dliappis dliappis self-assigned this Oct 5, 2017
@dliappis dliappis added the doc label Oct 5, 2017
@dliappis
Copy link
Contributor

dliappis commented Oct 5, 2017

Good catch! My suggestion is to remove this from the docker-compose prod example and include an additional note item to explain the disadvantage with setting this; I think it's still worth to remind that it is possible to limit the mem e.g. for people with limited mem due to defaults in Docker for Mac/Docker for Windows who may accept a performance penalty.

@dliappis
Copy link
Contributor

This has been tackled in the docs some time ago.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants