# Slow update when using vtkGlyph3D in Activiz 9.1
**URL:** https://discourse.vtk.org/t/slow-update-when-using-vtkglyph3d-in-activiz-9-1/9377
**Category:** Support
**Created:** [September 17, 2022, 2:22am UTC](https://discourse.vtk.org/t/slow-update-when-using-vtkglyph3d-in-activiz-9-1/9377 "2022-09-17T02:22:14Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@MarKara](https://discourse.vtk.org/u/MarKara)
#### Post date: [September 17, 2022, 2:22am UTC](https://discourse.vtk.org/t/slow-update-when-using-vtkglyph3d-in-activiz-9-1/9377/1 "2022-09-17T02:22:14Z")
Hi
I just moved from Activiz 6.3 to 9.1 and found that visualizing relatively large dataset with vtkGlyph3D is very very slow. I have 7746 points and it takes couple minutes to update glyphs.
In version 6.3, update and rendering is almost instant. I checked Paraview and works seamlessly.
Not sure if I’m missing some other settings, but this should be very simple. Attached is the polydata file I’m using for testing
Please advise.
Thanks
Marinko
[YXXJMDRJFZ.vtp](https://discourse.vtk.org/uploads/short-url/whMtSg5M3zL1Fp9WbcHWdmm9KEE.vtp) (1.2 MB)
```
vtkXMLPolyDataReader wr = new vtkXMLPolyDataReader();
wr.SetFileName(filename);
wr.Update();
vtkPolyData PD = new vtkPolyData();
PD = wr.GetOutput();
wr.Dispose();
vtkCubeSource cubeSource = new vtkCubeSource();
cubeSource.SetXLength(3);
cubeSource.SetYLength(3);
cubeSource.SetZLength(3);
sampleGlyph3D.SetInputData(Grid);
sampleGlyph3D.SetSourceConnection(cubeSource.GetOutputPort());
sampleGlyph3D.ScalingOff();
sampleGlyph3D.Update();
```
---
### Author:  [@toddy](https://discourse.vtk.org/u/toddy)
#### Post date: [September 17, 2022, 6:09am UTC](https://discourse.vtk.org/t/slow-update-when-using-vtkglyph3d-in-activiz-9-1/9377/2 "2022-09-17T06:09:59Z")
> [@MarKara](#):
>
> ```auto
> vtkPolyData PD = new vtkPolyData();
> PD = wr.GetOutput();
>
> ```
Why are you copying the poly data to a new object? Just hold onto the output.
`vtkPolyData PD = wr.GetOutput();`
---
### Author:  [@LucasGandel](https://discourse.vtk.org/u/LucasGandel)
#### Post date: [September 19, 2022, 7:19am UTC](https://discourse.vtk.org/t/slow-update-when-using-vtkglyph3d-in-activiz-9-1/9377/3 "2022-09-19T07:19:17Z")
I confirm it takes a minute with Activiz 9.1.2022.222 on my side, and 300ms with the nightly build of Activiz that is based on VTK-master. Both versions are built with STDThread as SMP backend.
So this is very likely to be fixed in the next Activiz version that should be release soon.
---
### Author:  [@toddy](https://discourse.vtk.org/u/toddy)
#### Post date: [September 20, 2022, 12:01am UTC](https://discourse.vtk.org/t/slow-update-when-using-vtkglyph3d-in-activiz-9-1/9377/4 "2022-09-20T00:01:35Z")
So this is a VTK regression rather than an Activiz problem?
---
### Author:  [@cory.quammen](https://discourse.vtk.org/u/cory.quammen)
#### Post date: [September 20, 2022, 2:37am UTC](https://discourse.vtk.org/t/slow-update-when-using-vtkglyph3d-in-activiz-9-1/9377/5 "2022-09-20T02:37:41Z")
There was a vtkGlyph3D performance regression fixed, I believe, by [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/8999](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8999).
---
### Author:  [@LucasGandel](https://discourse.vtk.org/u/LucasGandel)
#### Post date: [September 20, 2022, 6:23am UTC](https://discourse.vtk.org/t/slow-update-when-using-vtkglyph3d-in-activiz-9-1/9377/6 "2022-09-20T06:23:44Z")
Thanks @cory.quammen, this explains why other filters such as vtkExtractSelection are impacted too.
---
### Author:  [@MarKara](https://discourse.vtk.org/u/MarKara)
#### Post date: [September 23, 2022, 5:58pm UTC](https://discourse.vtk.org/t/slow-update-when-using-vtkglyph3d-in-activiz-9-1/9377/7 "2022-09-23T17:58:30Z")
Installed 9.2 and issue with 3D glyphs has been resolved.
Thanks Lucas
Found another problem that I’ll explain in next post