> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pdfm-ug/v26-zh-tw/parallels-desktop-for-mac-26-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/zui-jia-hua-xiao-neng/she-ding-fen-pei-gei-windows-de-ji-yi-ti.md).

# 設定分配給 Windows 的記憶體

設定 Parallels Desktop 會分配一定容量的 Mac 可用 RAM 記憶體給 Windows，而剩下的容量分配給 macOS。如果分配給 Windows 的容量太大，macOS 運行可能會變慢，反過來又會引起 Windows 應用程式運行緩慢，因為他們都在 macOS 上運行。另外，如果分配給 macOS 的容量太大，macOS 應用程式可能會運行良好但是 Windows 應用程式可能會變慢。

要最佳化 Windows 與 macOS 的效能，可設定分配給 Windows 的記憶體容量在建議範圍內。

要設定分配給 Windows 的記憶體容量：

1. [關閉 Windows](/landing/pdfm-ug/v26-zh-tw/parallels-desktop-for-mac-26-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/kai-shi-shi-yong/guan-bi-huo-zhong-zhi-windows.md)。
2. 選擇「**動作**」>「**設定**」>「**硬體**」>「**CPU 和記憶體**」。
3. 移動記憶體滑桿到建議範圍 (滑桿下有圖形顯示) 內的某個位置 (檢視以上描述)。<br>

   如果您使用需要很多記憶體的 Windows 應用程式，如 3D 或視訊製作應用程式，最好設定記憶體分配趨向範圍最高點 (移動滑桿至右邊)。或者通常最好是設定靠近中間。

{% hint style="info" %}
**附註：**&#x4E0D;管您的 Mac 有多少記憶體 (RAM)，可分配到 Windows 的最大記憶體容量是 8 GB。但是，如果您使用 Parallels Desktop for Mac Pro/Business/Enterprise Edition，分配給 Windows 的最大記憶體容量為 128 GB。
{% endhint %}

如果您變更了該設定然後您不喜歡 Windows 執行的方式，可嘗試不同的設定。

{% hint style="info" %}
**附註：**&#x5982;果您想要防止虛擬機器設定被未經授權地更改，請按一下位於視窗底部的鎖定圖示。下次如果想要在虛擬機器配置的任何窗格中變更設定，將需要管理員密碼。
{% 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 by asking a question.

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

```
GET https://docs.parallels.com/landing/pdfm-ug/v26-zh-tw/parallels-desktop-for-mac-26-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/zui-jia-hua-xiao-neng/she-ding-fen-pei-gei-windows-de-ji-yi-ti.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.