Are you using x forwarding when you connect to these machines? What is localhost:10.0 display to? Try running some other X-based application like gvim, or glxgears etc. and see where that window pops up. If it's popping up on your laptop, you're using X forwarding. Every render on the server will then be forwarding X calls to your laptop and that would explain the slow down.
If there an X server running on the "remote site"? If so, check with your sysadmin to get access to that X if possible. If not, you'll need to recoming with OSMesa, I am afraid. Utkarsh On Wed, May 20, 2015 at 1:07 AM, Noah Taylor <haonrol...@gmail.com> wrote: > Hello, > > I am using ParaView 4.0.1 since I developed a python script for > interpretation on this version. I am able to run ParaView fine on my local > Ubuntu Desktop. I have setup an EC2 AWS instance both a GPU and a CPU > instance both running Ubuntu but they both are giving me the same problem of > very very slow rendering for each time step with the offscreen rendering > option turned on. I also run into this problem on a Unix supercomputer I am > trying to run my code on. On my local machine it takes less than a second > for each time step I am rendering to be outputted with the same settings and > I am not spinning anything up like pvserver - on the node instances I have, > it is taking well around a minute or probably more for each frame. > > I have read through a lot of similar issues and the documentation for X > connections but I am not having any luck. The default DISPLAY is set to the > localhost:10.0 and I have tried changing that to the localhost:0.0 but it > gives me the bad -X connection error. From there, I followed previous > mailing list instructions and tried spinning up the pvserver (I don't know > why since I am not trying to serve anything just render frames) but I get an > error with the shared libraries that they're too short. I am using the > default downloadable version of 4.0.1 since I want to try and keep this as > simple as possible but I don't know if these have the mpi turned on by > default. Has anybody ran into this Bad X Connection issue and found an easy > way around it besides messing with the OSMesa and recompiling? I'd really > appreciate any pointers :) > > Thanks, > Noah > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview