# Memory inspector not reflecting what is requested on Pvserver
**URL:** https://discourse.paraview.org/t/memory-inspector-not-reflecting-what-is-requested-on-pvserver/10538
**Category:** ParaView Support
**Created:** [October 17, 2022, 5:50pm UTC](https://discourse.paraview.org/t/memory-inspector-not-reflecting-what-is-requested-on-pvserver/10538 "2022-10-17T17:50:27Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@Hussein\_Kokash](https://discourse.paraview.org/u/Hussein_Kokash)
#### Post date: [October 17, 2022, 5:50pm UTC](https://discourse.paraview.org/t/memory-inspector-not-reflecting-what-is-requested-on-pvserver/10538/1 "2022-10-17T17:50:27Z")
Hello,
I am using reverse connection to connect to server using:
mpirun -np 16 --hostfile /etc/openmpi/openmpi-default-hostfile --host 141.217.21.148: ./pvserver -ch=localhost -rc --force-offscreen-rendering
It’s supposed to request 16 processors but the the actual use (in memory inspector) is less.
What could be the cause of that?
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 18, 2022, 1:19am UTC](https://discourse.paraview.org/t/memory-inspector-not-reflecting-what-is-requested-on-pvserver/10538/2 "2022-10-18T01:19:12Z")
Hi @Hussein_Kokash ,
Which version of ParaView are you using ?
Did you check that there is actually 16 pverserver running on your hosts ?
Was pvserver built with MPI support ?
What does the Help → About → Remote shows once connected ?
Best,
---
### Author:  [@Hussein\_Kokash](https://discourse.paraview.org/u/Hussein_Kokash)
#### Post date: [October 18, 2022, 6:20pm UTC](https://discourse.paraview.org/t/memory-inspector-not-reflecting-what-is-requested-on-pvserver/10538/3 "2022-10-18T18:20:19Z")
The version is 5.9.1
Yes I checked (on server through glances) and it is not showing that pvserver is using those 16 processors.
The third question am not sure about, but I used the MPI folder (ParaView-5.9.1-MPI-Linux-Python3.8-64bit) on the server.
This is the remote connection from About:
_Client Information:_
_Version: 5.9.1_
\*VTK Version: \*
_Qt Version: 5.12.9_
_vtkIdType size: 64bits_
_Embedded Python: On_
_Python Library Path: /home/hf9098/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/lib/python3.8_
_Python Library Version: 3.8.8 (default, May 17 2021, 15:58:51) [GCC 7.3.1 20180303 (Red Hat 7.3.1-5)]_
_Python Numpy Support: On_
_Python Numpy Path: /home/hf9098/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/lib/python3.8/site-packages/numpy_
_Python Numpy Version: 1.19.2_
_Python Matplotlib Support: On_
_Python Matplotlib Path: /home/hf9098/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/lib/python3.8/site-packages/matplotlib_
_Python Matplotlib Version: 3.2.1_
_Python Testing: Off_
_MPI Enabled: On_
_Disable Registry: Off_
\*Test Directory: \*
\*Data Directory: \*
_OpenGL Vendor: Intel Open Source Technology Center_
_OpenGL Version: 4.6 (Core Profile) Mesa 20.0.8_
_OpenGL Renderer: Mesa DRI Intel(R) UHD Graphics (CML GT2)_
_Connection Information:_
_Remote Connection: Yes_
_Separate Render Server: No_
_Reverse Connection: Yes_
_Number of Processes: 1_
_Disable Remote Rendering: Off_
_IceT: Off_
_Tile Display: Off_
_vtkIdType size: 64bits_
_Embedded Python: On_
_Python Library Path: /home/hf9098/ParaView-5.9.1-osmesa-MPI-Linux-Python3.8-64bit/lib/python3.8_
_Python Library Version: 3.8.8 (default, May 17 2021, 15:56:25) [GCC 7.3.1 20180303 (Red Hat 7.3.1-5)]_
_Python Numpy Support: On_
_Python Numpy Path: /home/hf9098/ParaView-5.9.1-osmesa-MPI-Linux-Python3.8-64bit/lib/python3.8/site-packages/numpy_
_Python Numpy Version: 1.19.2_
_Python Matplotlib Support: On_
_Python Matplotlib Path: /home/hf9098/ParaView-5.9.1-osmesa-MPI-Linux-Python3.8-64bit/lib/python3.8/site-packages/matplotlib_
_Python Matplotlib Version: 3.2.1_
_OpenGL Vendor: VMware, Inc._
_OpenGL Version: 3.3 (Core Profile) Mesa 18.2.2_
_OpenGL Renderer: llvmpipe (LLVM 7.0, 256 bits)_
_Headless support: OSMesa_
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 19, 2022, 1:09am UTC](https://discourse.paraview.org/t/memory-inspector-not-reflecting-what-is-requested-on-pvserver/10538/4 "2022-10-19T01:09:23Z")
> [@Hussein\_Kokash](#):
>
> it is not showing that pvserver is using those 16 processors.
Then you are either not using the mpirun command you shared above or you have a big issue with your mpi installation.
For comparison on my machine:
```auto
$ mpirun -np 4 ./bin/pvserver &
[1] 7048
Waiting for client...
Connection URL: cs://frollo:11111
Accepting connection(s): frollo:11111
$ pf -ef | grep pvserver
glow 7048 1498 1 09:08 pts/0 00:00:00 mpirun -np 4 ./bin/pvserver
glow 7053 7048 4 09:08 pts/0 00:00:00 ./bin/pvserver
glow 7054 7048 89 09:08 pts/0 00:00:05 ./bin/pvserver
glow 7055 7048 90 09:08 pts/0 00:00:05 ./bin/pvserver
glow 7056 7048 89 09:08 pts/0 00:00:05 ./bin/pvserver
glow 7071 1498 0 09:08 pts/0 00:00:00 grep pvserver
```
Best,
---
### Author:  [@Hussein\_Kokash](https://discourse.paraview.org/u/Hussein_Kokash)
#### Post date: [October 19, 2022, 3:13pm UTC](https://discourse.paraview.org/t/memory-inspector-not-reflecting-what-is-requested-on-pvserver/10538/5 "2022-10-19T15:13:22Z")
Hello Mathieu,
What makes it confusing is that when I use the mpirun command with ./pvserver, it connects to paraview on my local machine (reverse connection) so when I the connection is accepted, It makes it even more confusing on why it didn’t reserve those processors.
I will keep looking into this and see what could be the cause.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 20, 2022, 1:32am UTC](https://discourse.paraview.org/t/memory-inspector-not-reflecting-what-is-requested-on-pvserver/10538/6 "2022-10-20T01:32:42Z")
before doing any kind of connection, you want to check that your pvserver are actually distributed.
```auto
mpirun -np 4 ./pvserver
```
Should not output any error and you should be able to see the four processes running, in active waiting.
---
### Author:  [@Hussein\_Kokash](https://discourse.paraview.org/u/Hussein_Kokash)
#### Post date: [October 20, 2022, 3:44pm UTC](https://discourse.paraview.org/t/memory-inspector-not-reflecting-what-is-requested-on-pvserver/10538/7 "2022-10-20T15:44:23Z")
It seems that there is indeed a problem with setting up parallel processing.
When this command is used “./pvserver -ch=localhost -rc --server-port=11111 --force-offscreen-rendering” there is absolutely no problem.
I want to ask something, I have completed the setup on my local machine (in terms of paraview build), while on server I just copied the folder “ParaView-5.9.1-MPI-Linux-Python3.8-64bit” and paste it there.
Is there a compilation process needed to be done on the server side, knowing that MPI and OSMesa are working there.
Thanks again Mathieu!
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 21, 2022, 1:27am UTC](https://discourse.paraview.org/t/memory-inspector-not-reflecting-what-is-requested-on-pvserver/10538/8 "2022-10-21T01:27:37Z")
use the mpiexec provided in the package
`./mpiexe -np 4 ./pvervser`
---
### Author:  [@Hussein\_Kokash](https://discourse.paraview.org/u/Hussein_Kokash)
#### Post date: [October 22, 2022, 4:15am UTC](https://discourse.paraview.org/t/memory-inspector-not-reflecting-what-is-requested-on-pvserver/10538/9 "2022-10-22T04:15:32Z")
Finally!!!
Thank you Mathieu!
