> 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/help-center-fr/general-faq/how-long-should-it-take-to-index-assets.md).

# Combien de temps prend l’indexation ?

Notre indexation est conçue pour gérer des millions d’actifs

Notre système actuel dispose d’un ensemble de nœuds d’indexation qui indexent tous vos éléments sur une variété de tâches différentes selon le type d’élément. En général, les tâches les plus longues sont la génération des proxys, ainsi que notre tâche principale de vision qui exécute les embeddings et des métadonnées supplémentaires.

Les derniers benchmarks indiquent que nos proxys fonctionnent généralement à 16 fois la cadence d’image de votre vidéo ; toutefois, divers facteurs peuvent y contribuer, notamment la quantité de fichiers que vous avez importés à un moment donné, et plus encore. Shade fera de son mieux pour analyser et traiter les fichiers selon le principe premier importé, premier indexé.  


---

# 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/help-center-fr/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.