# paraview load a VTK File wait for few minutes
**URL:** https://discourse.paraview.org/t/paraview-load-a-vtk-file-wait-for-few-minutes/1022
**Category:** Development
**Created:** [December 9, 2018, 6:53am UTC](https://discourse.paraview.org/t/paraview-load-a-vtk-file-wait-for-few-minutes/1022 "2018-12-09T06:53:29Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@arthur](https://discourse.paraview.org/u/arthur)
#### Post date: [December 9, 2018, 6:53am UTC](https://discourse.paraview.org/t/paraview-load-a-vtk-file-wait-for-few-minutes/1022/1 "2018-12-09T06:53:29Z")
hi evevyone, recently,I Build paraview source with CMake and vs2015 with QT5.10,It build seccused,but when I use paraview.exe which created by vs2015 ,the paraview load a VTK File wait for few minutes,it is too slower than the published paraview.exe.Is there someone meet with this problem？ some one can tell me how to speed up this.thx!!!
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [December 10, 2018, 1:45pm UTC](https://discourse.paraview.org/t/paraview-load-a-vtk-file-wait-for-few-minutes/1022/2 "2018-12-10T13:45:33Z")
Did you build in Debug mode? With MSVC, Debug builds are substantially slower than Release builds (which is the mode the published paraview.exe was built with). This is particularly true when it comes to parsing ASCII text files, which I am assuming your VTK file is. You can try to work around this by saving the VTK file as a binary file, which will be much faster to load in both Release and Debug modes. Or you can just rebuild in Release mode.
---
### Author:  [@arthur](https://discourse.paraview.org/u/arthur)
#### Post date: [December 10, 2018, 2:01pm UTC](https://discourse.paraview.org/t/paraview-load-a-vtk-file-wait-for-few-minutes/1022/3 "2018-12-10T14:01:01Z")
yes，I know Debug mode is slower than release builds,and i also had tried the release build mode,it is faster a little,but it also load vtk File slowly;yes, the vtk file is ASCII one,but when i use the published paraview.exe to load the same vtk file,it more fast. I dont konw when the paraview load the file,I clicked the Open File,selected my file path,in the pipeline brower can see the name of vtk,when i clicked the icon(which look like an eye),the sofware will be hold on and i must wait for about 2min,it can finish loading the model in the graphic view.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [December 10, 2018, 2:44pm UTC](https://discourse.paraview.org/t/paraview-load-a-vtk-file-wait-for-few-minutes/1022/4 "2018-12-10T14:44:35Z")
That’s interesting. I’m not sure what else might explain the slowdown.
---
### Author:  [@arthur](https://discourse.paraview.org/u/arthur)
#### Post date: [December 10, 2018, 2:50pm UTC](https://discourse.paraview.org/t/paraview-load-a-vtk-file-wait-for-few-minutes/1022/5 "2018-12-10T14:50:54Z")
thanks for your reply.I not sure… Is the MPI\_module has relationship about files loading？Maybe some module is not available？
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [December 10, 2018, 4:54pm UTC](https://discourse.paraview.org/t/paraview-load-a-vtk-file-wait-for-few-minutes/1022/6 "2018-12-10T16:54:35Z")
Not sure if this is the issue, but don’t forget about caching issues. The first time the dataset is loaded, it comes from disk. The second time, it probably comes from cache (depending on the size of the dataset). So, if you try your debug build first, and a Kitware release build second, the release build will be much faster. Always use the second load of your data for performance tests.
---
### Author:  [@arthur](https://discourse.paraview.org/u/arthur)
#### Post date: [December 11, 2018, 12:08am UTC](https://discourse.paraview.org/t/paraview-load-a-vtk-file-wait-for-few-minutes/1022/7 "2018-12-11T00:08:43Z")
Yep it the second time load the vtk from cache,it is
Also performance much slowly(about 2min)than I used the published paraview.exe(just 15seconds).
[
](https://maas.mail.163.com/dashi-web-extend/html/proSignature.html?iconUrl=http%3A%2F%2Fmail-online.nosdn.127.net%2F1862deeec222c8022616f074ad517763.jpg&name=%E7%86%8A70&uid=example%40163.com&ftlId=3&items=%5B%22%E9%82%AE%E7%AE%B1%EF%BC%9Aarthur314%40163.com%22%5D)
熊70
邮箱：arthur314@163.com
签名由 [网易邮箱大师](https://mail.163.com/dashi/dlpro.html?from=mail88) 定制
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [December 11, 2018, 5:58pm UTC](https://discourse.paraview.org/t/paraview-load-a-vtk-file-wait-for-few-minutes/1022/8 "2018-12-11T17:58:15Z")
MPI should not be a factor. The Kitware binaries are built with Intel’s Thread Building Blocks as the multithreading backend, which is used to accelerate some algorithms, but not the reader as far as I know. Could you compare the CPU usages between the two versions? If you have a multicore system and the Kitware ParaView uses all your cores at near 100% while your built version does not use all the cores, that could be the difference.