> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/help-center/general-faq/how-long-should-it-take-to-index-assets.md).

# How long does indexing take?

Our indexing is designed to handle millions of assets

Our current system has a set of indexer nodes that index all of your assets across a variety of different jobs depending on the asset type. Typically, the longest jobs are proxy generation, and our core vision job that runs the embeddings and additional metadata.

Latest benchmarks suggest that our proxies typically run at 16x the frame-rate of your video, however various factors can contribute to this depending on the amount of files you've uploaded at a given time and more. Shade will do its best to parse and process files on a first upload first index basis. &#x20;


---

# 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://academy.shade.inc/help-center/general-faq/how-long-should-it-take-to-index-assets.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.
