# Octree support
**URL:** https://discourse.paraview.org/t/octree-support/2228
**Category:** ParaView Support
**Created:** [July 15, 2019, 7:39pm UTC](https://discourse.paraview.org/t/octree-support/2228 "2019-07-15T19:39:18Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Fayanzar](https://discourse.paraview.org/u/Fayanzar)
#### Post date: [July 15, 2019, 7:39pm UTC](https://discourse.paraview.org/t/octree-support/2228/1 "2019-07-15T19:39:18Z")
Dear all,
I’ve experienced such a problem: so far I have the octree-structured data represented with separate cells in hdf5/xdmf format. The thing is, handling large data in such a format causes significant RAM blowups. Is there native octree support (or some thrid-party plugins) which would allow reducing the amount of memory needed to work with all that stuff (for instance, represent it in some other way, not storing all the cells as separate pieces of data)? It would be great to preserve the current format, but if it’s impossible, any other solution is welcome.
Best,
Dmytro
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [July 16, 2019, 11:29am UTC](https://discourse.paraview.org/t/octree-support/2228/2 "2019-07-16T11:29:23Z")
Are you looking for an AMR based dataset ?
> **[Visualization & Analysis of AMR Datasets - Kitware Blog](https://blog.kitware.com/visualization-analysis-of-amr-datasets/)**
>
> Multiphysics simulations of complex phenomena exhibiting large length and time scales, such as astrophysics, have been greatly facilitated by the AMR approach. By discretizing the ... Read More
---
### Author:  [@Dave\_DeMarle](https://discourse.paraview.org/u/Dave_DeMarle)
#### Post date: [July 17, 2019, 6:39pm UTC](https://discourse.paraview.org/t/octree-support/2228/3 "2019-07-17T18:39:13Z")
VTK’s HyperTreeGrid data type could be a closer match to your format (tree based rather than the block structured AMR that Mathieu suggested).
Note that the HTG code prior to 5.6 didn’t get sufficient attention from users or developers and grew very buggy over time. We are actively working on it once more though and have fixed a number of bugs and added some new features, so 5.7 could be a good time to try it. See the VTK level regression tests and the Random Source in ParaView for some idea of what it is like.