> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/space/structure-limits.md).

# Structure Limits

To help you get the best performance from your workspace, we've outlined a set of recommended guidelines. These guidelines are based on our internal benchmarks and real-world usage to ensure your experience remains smooth, responsive, and scalable.

The limits are presented as individual values for clarity, but it’s important to keep in mind that they can interfere with each other.

The individual application components all work together and share system resources. This means that overall performance depends on how these elements are combined.

Think of the application as a **connected environment**. These limits are not strict ceilings, but rather helpful reference points to guide planning and scale confidently. By staying mindful of the overall structure, you can build powerful, flexible spaces that perform well.

## 📊 Recommended Soft Limits

| Limit             | Value                                         |
| ----------------- | --------------------------------------------- |
| Rules and folders | 500 rules / 100 folders / 5 levels of nesting |
| Table rows        | 40 000                                        |
| Table columns     | 40                                            |
| Table cells       | 80 000                                        |
| Tree nodes        | 600                                           |
| Script lines      | 100 000                                       |
| Workflow nodes    | 150                                           |
| Import            | 100 MB                                        |
| Folder export     | 40 MB (default); configurable for on-prem/PMC |

By keeping your structure balanced and monitoring performance as you grow, you can scale effectively while maintaining a great user experience. Whether you're building something small or expanding into something much bigger, these guidelines are here to support you.


---

# 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.decisionrules.io/doc/space/structure-limits.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.