> For the complete documentation index, see [llms.txt](https://tg-qisi-tae.gitbook.io/tg.qisi_tae-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tg-qisi-tae.gitbook.io/tg.qisi_tae-docs/06-zhi-neng-tui-jian-pei-zhi-yu-zi-yuan-jian-kong.md).

# 06 智能推荐配置与资源监控

根据电脑配置推荐并发，并实时查看CPU、内存和活动连接。

系统设置集中管理连接上限、日志保留、智能推荐并发和本机资源占用。

![系统设置与资源监控](https://3113701068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3h2NgAnxHRZdWHkoarUV%2Fuploads%2FPVmg6jt4D0dcRMJWN5YU%2F01-system-settings.jpg?alt=media)

## 推荐配置

1. 在 **计划运行账号** 中填写准备参与任务的账号数。
2. 选择运行侧重，例如均衡运行或性能优先。
3. 点击 **检测并推荐**。
4. 检查推荐值后点击 **一键应用**。

推荐值是起点，不是强制上限。电脑配置较高、代理质量稳定时可以继续手动调整。

## 左下角实时状态

软件左下角持续显示 CPU、内存和活动连接。监控采用低频刷新，不会形成明显额外负担。

{% hint style="warning" %}
如果 CPU 长时间超过 85%、可用内存低于约 2GB，或代理连接连续失败，应降低并发，等待运行恢复后再逐步提高。
{% 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://tg-qisi-tae.gitbook.io/tg.qisi_tae-docs/06-zhi-neng-tui-jian-pei-zhi-yu-zi-yuan-jian-kong.md?ask=<question>&goal=<endgoal>
```

`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.