# Poor GUI performance when building from source
**URL:** https://discourse.paraview.org/t/poor-gui-performance-when-building-from-source/1264
**Category:** ParaView Support
**Created:** [February 9, 2019, 7:12pm UTC](https://discourse.paraview.org/t/poor-gui-performance-when-building-from-source/1264 "2019-02-09T19:12:34Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Derrick63](https://discourse.paraview.org/u/Derrick63)
#### Post date: [February 9, 2019, 7:12pm UTC](https://discourse.paraview.org/t/poor-gui-performance-when-building-from-source/1264/1 "2019-02-09T19:12:35Z")
Ubuntu 16.04
Paraview 5.6 (Both release and super-build)
gcc 8.1.0
qt 5.12.0
I’ve been able to build Paraview from source without any errors but when I run the program, the gui performance is very slow without even loading any data in the program. For example: delayed response to menu picks and delayed movement of axis in graphics window. When I download and run from the pre-built binaries, the gui response is good. So it’s something in the build process that’s affecting the program performance. Anyone have any ideas on where to start looking?
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [February 11, 2019, 3:05pm UTC](https://discourse.paraview.org/t/poor-gui-performance-when-building-from-source/1264/2 "2019-02-11T15:05:24Z")
That is a pretty standard build setup, I think. It could be Qt 5.12.0. I think @utkarsh.ayachit has encountered some problems with that version (not sure about performance issues). FYI, we are building the pre-built binaries on linux are using Qt 5.10.1.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [February 11, 2019, 3:11pm UTC](https://discourse.paraview.org/t/poor-gui-performance-when-building-from-source/1264/3 "2019-02-11T15:11:04Z")
FYI I’m building with Qt 5.12.1 (ArchLinux) without any issue here.
---
### Author:  [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [February 11, 2019, 3:19pm UTC](https://discourse.paraview.org/t/poor-gui-performance-when-building-from-source/1264/4 "2019-02-11T15:19:30Z")
> [@cory.quammen](#):
>
> It could be Qt 5.12.0. I think @utkarsh.ayachit has encountered some problems with that version (not sure about performance issues)
I was referring to Qt 5.12.0 and macOS Mojave. I haven’t had issues with 5.12 on other platforms or older versions of macOS.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [February 11, 2019, 3:46pm UTC](https://discourse.paraview.org/t/poor-gui-performance-when-building-from-source/1264/5 "2019-02-11T15:46:30Z")
Okay, thanks for clarifying @utkarsh.ayachit and @mwestphal.
---
### Author:  [@Derrick63](https://discourse.paraview.org/u/Derrick63)
#### Post date: [February 12, 2019, 8:24pm UTC](https://discourse.paraview.org/t/poor-gui-performance-when-building-from-source/1264/6 "2019-02-12T20:24:44Z")
Thanks for everyone’s inputs. They’ve been very helpful in narrowing down the problem. I had been building Paraview with the “USE\_SYSTEM\_qt5” option to cut down on build time. I recompiled without that option and the gui is performing fine now. My system qt5 is version 5.12 from source. I noticed that in the superbuild, qt5 is built with the following options that are not included in my system qt5 build:
-top-level
-skip qtconnectivity
-skip qtgamepad
-skip qtlocation
-skip qtmultimedia
-skip qtsensors
-skip qtserialport
-skip qtwayland
-skip qtwebchannel
-skip qtwebengine
-skip qtwebsockets
-nomake examples
-nomake tests
-no-dbus
-qt-libjpeg
-qt-pcre
-system-zlib
-no-openssl
-skip qtsvg
-qt-xcb
-system-libpng
I assume all these options were implemented for good reasons and I suspect one or more of these options is affecting the gui performance.