> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/zui-zhong-yong-hu-yu-he-zuo-huo-ban/end-user-section/our-document-priority-system.md).

# 我们的文档优先级系统

在我们的文档处理系统中，我们每天处理来自多个客户的大量文档。为确保及时处理每位客户的文档，我们实施了一套完善的优先级系统。该系统会根据客户的待处理文档数量动态调整优先级，确保**公平性**和**效率**。下面介绍优先级系统的工作方式，以及任务计数器何时重置。

**优先级系统的关键概念**

我们的优先级系统围绕几个关键概念运行：

1. **待处理文档**：指客户已提交但尚未处理的文档数量。
2. **重置间隔**：系统会定期将待处理文档计数重置为零，以确保没有客户能够无限期独占处理资源。

**优先级的确定方式**

以下是文档处理优先级的确定步骤：

1. **跟踪待处理文档**：每位客户都有一个待处理文档计数。这个计数用于了解每位客户有多少文档正在等待处理。
2. **重置计数**：为保持公平，如果自上次更新以来已超过设定的时间（即重置间隔），我们会将待处理文档计数重置为零。默认重置间隔为 1500 秒（即 25 分钟）。
3. **更新计数**：如果尚未达到重置间隔，每次检查时都会将待处理文档计数减一，以模拟处理一份文档。
4. **设置优先级**：处理任务的优先级取决于待处理文档的数量。待处理文档越少，优先级越高，这意味着这些任务会更早处理。我们设置了具体阈值，将优先级分为 1（最高）到 9（最低）。

**优先级级别**

优先级级别根据待处理文档计数按以下规则分配：

* **优先级 9**：待处理文档计数小于 -20 时
* **优先级 8**：待处理文档计数小于 -14 时
* **优先级 7**：待处理文档计数小于 -12 时
* **优先级 6**：待处理文档计数小于 -10 时
* **优先级 5**：待处理文档计数小于 -8 时
* **优先级 4**：待处理文档计数小于 -6 时
* **优先级 3**：待处理文档计数小于 -4 时
* **优先级 2**：待处理文档计数小于 -2 时
* **优先级 1**：待处理文档计数大于或等于 -2 时

{% hint style="info" %}
简单来说，待处理文档数量增加时，优先级级别会降低，这意味着这些文档会比优先级更高的其他文档更晚处理。
{% endhint %}

**计数器重置时间**

如果自上次更新以来已超过重置间隔（**1500** 秒），待处理文档计数器就会重置为零。此机制可确保没有客户能够无限累积待处理文档并占用系统资源。通过定期重置计数器，我们可以确保每位客户都能公平地获得处理时间。


---

# 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.docbits.com/chinese/zui-zhong-yong-hu-yu-he-zuo-huo-ban/end-user-section/our-document-priority-system.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.