> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/software/on-premises-software/software-on-premises-software-faq-list/000006042.md).

# Can a 10 Gbps connection support data analysis between the DRAGEN server and storage server?

**Can a 10 Gbps connection support data analysis between the DRAGEN server and storage server? Will the connection be stable?**

Yes, the DRAGEN server is designed to be used with a storage system and 10 Gbps is the recommended connection speed. As long as the connection between the DRAGEN server and storage unit is stable, users should not experience any issues with the analysis. Each lab's networking environment is unique. Illumina recommends that users consult with their IT department to confirm that the networking setup meets the recommended specifications for DRAGEN. DRAGEN will run at speed if there is a sustained IO of 300Mbytes/sec with the storage system. If data IO is slow, DRAGEN will run slower. If there is very high latency, DRAGEN runs watchdog timers that will trigger an error rather than wait for a long time.

*Note: The default storage location for intermediate analysis files is the* --output-directory *specified. To avoid I/O latency when using a networked output location, use the* --intermediate-results-dir *argument to set a local directory (eg, /staging/tmp) as the scratch space for DRAGEN.*

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                 |
| :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #6042), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000006042%20-%20Software%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# 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://knowledge.illumina.com/software/on-premises-software/software-on-premises-software-faq-list/000006042.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.
