# GPU Resident Drawer

Flora and Unity GPU Resident Drawer solve similar rendering problems with different content ownership models.

## Guidance

* Use Flora when you need terrain foliage support, container workflows, or runtime-created instance populations.
* Use GPU Resident Drawer for MeshRenderer-driven workflows where its defaults fit your project.

## What This Affects

* Memory footprint at high instance counts.
* Authoring workflow (`GameObject`-centric vs data-driven instancing).
* Occlusion workload if both systems run.

***

## Content Model Differences

* **GPU Resident Drawer**: active `GameObject` + `MeshRenderer` driven.
* **Flora**: supports terrain, containers, and runtime instance data without requiring one render `GameObject` path per instance.

Related Flora workflows:

* [Terrain Provider](/scripts/terrain-provider.md)
* [Instance Container](/scripts/instance-container.md)
* [Runtime Samples](/samples/runtime-samples.md#fish-boids)

***

## Occlusion Interaction

Both systems maintain separate occlusion resources. Running both over overlapping content can duplicate GPU work.

## Practical Recommendation

For the same content path, prefer one primary instancing/occlusion strategy and profile scene cost.


---

# Agent Instructions: 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:

```
GET https://flora.magneticarcade.com/rendering/gpu-resident-drawer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.