The thread discusses how to limit the maximum RAM usage for memory-mapped files in Windows, specifically targeting Elasticsearch to prevent large garbage collection pauses caused by memory paging. The original poster questions whether Windows or individual processes can be constrained in this way, noting that Elasticsearch's JVM heap size settings do not control memory-mapped file usage. A responder suggests consulting Elasticsearch documentation or support, implying that memory-mapped file sizes are managed internally by the application itself. Overall, the conversation indicates that restricting memory-mapped files may require application-specific adjustments rather than system-wide configurations.
