# how to create a distributed dataset

**URL:** https://discourse.paraview.org/t/how-to-create-a-distributed-dataset/1862
**Category:** Tips and Tricks
**Created:** [May 15, 2019, 5:16pm UTC](https://discourse.paraview.org/t/how-to-create-a-distributed-dataset/1862 "2019-05-15T17:16:57Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [May 15, 2019, 5:16pm UTC](https://discourse.paraview.org/t/how-to-create-a-distributed-dataset/1862/1 "2019-05-15T17:16:57Z")

</div>

From a support ticket reply from @mwestphal  
With unstructured grids, such as a single vtu file, the distribution of data is not free and has to be done explicitly.  
One way to do that is to use the D3 filter, like this :

```
Run pvserver in parallel
Run paraview, connect to pvserver
Open your .vtu file, Apply, it is not distributed
Add a D3 filter, Apply (can take some time) , dataset is now distributed
Save as a .pvtu file

```

Reopening this .pvtu file on a parallel paraview will give you a (statically) distributed dataset, while working with D3 directly will give you a dynamically distributed dataset but take more time each time you want to distribute your dataset.