> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/docker/docker-hardening-guide/test-the-memory-limit.md).

# Test the Memory Limit

Test Docker memory limits configured for Cortex XSOAR 6.14 containers.

After configuring the memory limitation to the recommend 1 GB, you can test the memory limit in the playground.

* Run the following automation script:

  ```screen
  from multiprocessing import Process
  import os


  def big_string(size):
      sys.stdin = os.fdopen(0, "r")
      s = 'a' * 1024
      while len(s) < size:
          s = s * 2
      print('completed creating string of length: {}'.format(len(s)))


  size = 1 * 1024 * 1024 * 1024
  p = Process(target=big_string, args=(size, ))
  p.start()
  p.join()
  if p.exitcode != 0:
      return_error("Return code from sub process indicates failure: {}".format(p.exitcode))
  else:
      print("Success allocating memory of size: {}".format(size))
  ```

  The command returns an error when it fails to allocate 1 GB of memory. For example:

  ![docker-test-memory.png](https://3548014557-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOHlpKeFtqCLUYKuYyccd%2Fuploads%2Fgit-blob-dd195581f58ebff59473afd1c1b889a5589766a1%2F5f537172529cc1e8519d7a51776d897e5b4c2bcf397dec12433275a200304a3e.png?alt=media)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/docker/docker-hardening-guide/test-the-memory-limit.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.