pvbatch with osmesa runs slower

I’m post-processing my OpenFOAM results on a remote server.
Option A: I run pvserver that is built with OpenFOAM on remote server, connect from my local machine and save animation (via on-screen rendering). Both server and client runs 5.4.
Option B: I directly parallel run pvbatch which I have downloaded with osmesa. This is version 5.6.
Both are on the same number of cores, but option B runs significantly slower. Is it something related to version, or CPU/GPU?
Thanks in advance.

As you perhaps know, OSMesa is not going to use your GPU, so there is a good chance that it is slower than Option A because of that. In Option A, are you doing remote rendering on the server?

To expand on what Cory said, check the preferences/settings under the Render tab and look at the client vs remote rendering threshold setting. If the visible geometry size is less than the threshold, the server ships the geometry to the client and the client side does the rendering. Otherwise the server side does the job and ships images to the client instead.

Hello, sorry for the late reply.
In option A, as far as I know, I am not doing the rendering on my local machine. Because, during the rendering process, black windows are launched up on my local machine, which are as many as the number of processes.
I am looking for a method to do the rendering on the remote server. But we do not have GPU on the nodes, only GPU is available on the head node. What I understand from the wiki page is, instead of running pvserver on a node, I should run pvrenderserver on the headnode and pvdataserver on a node, separately. Besides the fact that there are no guidelines on the wiki page on how to run them separately, I see that that is not very efficient.
So for now, my best bet is to run calculations on the server via job submission, but also during the calculation, do the rendering on my local machine. Is this possible?

I would not advise using the separate pvrenderserver and pvdataserver. If there are no GPUs on your compute nodes, then the osmesa version of pvbatch is your best bet.

I assume by running calculations you mean running something that is producing the data. If that is the case, then you can periodically select the File -> Reload Files menu item to load the latest data, then save an image of the updated data. This is likely to be no fun for you, however.

What you are describing is a perfect use case for ParaView’s Catalyst feature for in situ visualization. See https://www.paraview.org/in-situ/ for more details.