> For the complete documentation index, see [llms.txt](https://hi-primus.gitbook.io/bumblebee/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hi-primus.gitbook.io/bumblebee/help/bigger-than-memory-data.md).

# Bigger than memory data

In some scenarios the data you want to load could be bigger that your system or cluster memory which could cause slowdown or crash the system depending on the engine you are select.

To handle this we recommend:

1. Just select the number of rows you want to load when previewing the file in Bumblebee. When saving your processed data you can decide if to process the whole dataset.
2. Use Vaex as Bumblebee Engine. It can handle greater than memory data processing. 
3. If you have access to Dask/Dask-cuDF cluster use it. If your data is smaller than the total cluster memory it can slow thing down.
4. Use an external service like Coiled to load as much data as you need. With Coiled you can get a Dask/Dask-cuDF cluster on demand and pay for what you use.

I raise and issue about automatically load as much data as possible depending on the memory available. You can see it here.

Please let me know if you have another question.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hi-primus.gitbook.io/bumblebee/help/bigger-than-memory-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.