> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-client/technical-references/resource-utilization.md).

# Patch My PC Client Resource Utilization

*Applies to: Patch My PC Client*

The Patch My PC (PMPC) Client has the following expected resource utilization characteristics:

* **CPU usage -** When the Client is idle, CPU usage is typically expected to remain very low. However, it will increase temporarily during active operations such as inventory and policy evaluation.
* **Memory usage -** Memory usage for the Client will generally be around 70 MB during normal background operations. However, this will increase temporarily during active operations.
* **Resource usage -** Resources consumed by the Client tend to be burst-oriented rather than sustained, given its defined schedule intervals. See [Inventory Data](/patch-my-pc-cloud/insights-intune/technical-references/client-data-collection.md#inventory-data) for more information on intervals.

{% hint style="info" %}
**Note**

This article will be updated as additional features are added to the PMPC Client.
{% endhint %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.patchmypc.com/patch-my-pc-client/technical-references/resource-utilization.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 `build a script that syncs our docs to a CMS` 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.