> For the complete documentation index, see [llms.txt](https://jembi.gitbook.io/openhim-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jembi.gitbook.io/openhim-platform/guides/resource-allocations.md). # Resource Allocations ## What it Means ### CPU CPU allocations are specified as a portion of the total number of cores on the host system, i.e., a CPU limit of `2` in a `6-core` system is an effective limit of `33.33%` of the CPU, and a CPU limit of `6` in a `6-core` system is an effective limit of `100%` of the CPU. ### RAM Memory allocations are specified as a number followed by their multiplier, i.e., 500M, 1G, 10G, etc. ## Defaults As a default, each package contained in Platform is allocated a maximum of 3 GB of RAM, and 100% CPU usage. ## Allocating Resources per Package The resource allocation can be set on a per-package basis, as specified by the relevant environment variables found in the relevant [Packages section](/openhim-platform/packages.md). ## Notes * Be wary of allocating CPU limits to ELK Stack services. These seem to fail with CPU limits and their already implemented health checks. * Take note to not allocate less memory to ELK Stack services than their JVM heap sizes. * Exit code 137 indicates an out-of-memory failure. When running into this, it means that the service has been allocated too little memory. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://jembi.gitbook.io/openhim-platform/guides/resource-allocations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.