> For the complete documentation index, see [llms.txt](https://docs.velogicfit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velogicfit.com/zh/di-01-jie-ru-men/submitting-performance-data.md).

# 提交性能数据

收集并向 Velogic 支持提交性能数据以排查系统性能问题的说明。

如果您没有获得 Velogic Studio 期望中的性能表现，第一步很好的做法是向我们的支持团队提交一些性能数据。

如果我们的支持团队向您索取性能数据，请按以下步骤操作：

1. 像平常一样登录 Velogic Studio。
2. 进入应用程序中出现性能问题的地方。
3. 按下键盘上的 F12 键。这将打开“Tools”窗口。

> **注意：** “Tools”窗口主要用于内部使用，所以我们没有把它做得很好看！抱歉。

4. 点击“Performance”选项卡：

   ![](https://2529810062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjxwtZYYk0lvusnMTywNR%2Fuploads%2Fgit-blob-1fd20d4e44111de08cbaa2fb05d4d452f9e42aec%2Fsubmitting-performance-data.png?alt=media)
5. 点击“Collect performance data”按钮。第一次这样做时，可能需要几分钟来进行配置。
6. 最终您应该会看到：

   ![](https://2529810062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjxwtZYYk0lvusnMTywNR%2Fuploads%2Fgit-blob-3af2214673f78f490e5d5eb32483d830ee404809%2Fsubmitting-performance-data-1.png?alt=media)
7. 保持“Tools”窗口打开（您可以把它移动到其他屏幕或缩小它），返回 Velogic Studio，执行之前表现不佳的任务（例如：捕获、比较视频、生成报告）。
8. 完成该任务后，返回 Tools 窗口并点击“Stop collecting”

> **注意：** 性能数据可能很大——每秒采集大约 1MB。如果您的网络连接不佳，请尽量缩短采集性能数据的时间。

9. 点击“Stop collecting”后，系统需要几秒钟来准备提交数据。数据准备就绪后，您将看到：

   ![](https://2529810062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjxwtZYYk0lvusnMTywNR%2Fuploads%2Fgit-blob-71abb20cf80e4c1a3dfca9cb81ca619c834248a9%2FPasted%20image%2020250821111915.png?alt=media)
10. 点击“Submit to support”。

> **隐私说明：** 提交的数据完全是技术性的，只会告诉我们 Velogic Studio 各部分执行所需的时间。除您的电子邮件地址外，其中不包含任何用户数据。

11. 当数据已提交（上传）到我们的服务器后，性能选项卡将恢复到初始模式，仅显示“Collect performance data”按钮。现在您可以关闭 Tools 窗口。

我们的支持团队会收到该文件的通知，并会对其进行分析，然后通过电子邮件与您联系。

感谢您帮助让 Velogic Studio 变得更棒。


---

# 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.velogicfit.com/zh/di-01-jie-ru-men/submitting-performance-data.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.