You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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
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.
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.
The text was updated successfully, but these errors were encountered: