# Slow execution of Paraview 5.5 with Visual Studio 2017 debugger
**URL:** https://discourse.paraview.org/t/slow-execution-of-paraview-5-5-with-visual-studio-2017-debugger/722
**Category:** ParaView Support
**Created:** [October 12, 2018, 6:24pm UTC](https://discourse.paraview.org/t/slow-execution-of-paraview-5-5-with-visual-studio-2017-debugger/722 "2018-10-12T18:24:30Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@HollowSun0](https://discourse.paraview.org/u/HollowSun0)
#### Post date: [October 12, 2018, 6:24pm UTC](https://discourse.paraview.org/t/slow-execution-of-paraview-5-5-with-visual-studio-2017-debugger/722/1 "2018-10-12T18:24:30Z")
Hi,
Since I updated to PV 5.5, launching ParaView from the Visual Studio 2017 debugger now takes about 2 minutes. My build is configured to x64, RelWithDebInfo. Right now, I have configured my startup project to launch “Paraview”, and as soon as I press on “Start”, all “[…]Hierarchy” projects are triggered by the check. Is this normal?
Correct me if I’m unclear.
Thank you!
Patrick
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [October 15, 2018, 12:55pm UTC](https://discourse.paraview.org/t/slow-execution-of-paraview-5-5-with-visual-studio-2017-debugger/722/2 "2018-10-15T12:55:51Z")
There was a report of Hierarchy commands being run unnecessarily. This should be fixed with the new module system (due by the end of the year to `master` at least). If you use `ninja`, the output of `ninja -d explain` can show why it thinks it needs to rerun the targets (VS may also have this information, but I don’t know how to get it).
---
### Author:  [@HollowSun0](https://discourse.paraview.org/u/HollowSun0)
#### Post date: [October 15, 2018, 1:57pm UTC](https://discourse.paraview.org/t/slow-execution-of-paraview-5-5-with-visual-studio-2017-debugger/722/3 "2018-10-15T13:57:06Z")
Thanks! I shall wait until next year then.
Patrick