> For the complete documentation index, see [llms.txt](https://docs.marpledata.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.marpledata.com/docs/marple-db/datastreams/ingestion-queue.md).

# Ingestion Queue

When you upload files, they enter the ingestion queue. By default, Marple DB will import up to 2 files in parallel. Any other files wait their turn and start importing as soon as a slot frees up.<br>

{% columns %}
{% column width="50%" %}
You can see the queue state on each file, or in the home screen:

* "Waiting" until a slot opens;
* "Importing" while it's being processed;
* "Imported" when it's ready.

For most teams the default is fine. Larger teams and higher data volumes\
can fill up this queue.
{% endcolumn %}

{% column width="50%" %} <img src="/files/KLM9NY7MMuERwiTkgkYw" alt="" data-size="original">

{% endcolumn %}
{% endcolumns %}

### Scaling with Ingestion Nodes

<figure><img src="/files/AqPSWcdXDgGfEOtocP6D" alt=""><figcaption></figcaption></figure>

Don't want to wait for slots to free up? Ingestion Nodes turn your queue into a fleet. Every upload runs on its own dedicated compute node, so the more nodes you have, the more files import in parallel.

* **No more queueing.** Files start importing the moment they arrive.
* **No more bottlenecks.** Each upload gets its own CPU and memory, so a multi-gigabyte file never holds up the small one behind it.
* **Unlimited thoughput.** Add capacity for a growing team, bigger files, or whenever you notice the queue filling up.

If you are interested in upgrading to more ingestion nodes, contact <sales@marpledata.com>.