[OpendTect_Developers] Remote 3D rendering/ Use of the GPU

[Julien Moreau]

Hello OdT Community,

I am a new to this list and I am not sure it is the right place to ask the question. However, I assume that you are probably the ones which are most likely to try this kind of operation.

For obvious economic reason and practicality I want to run OpendTect remotely on my workstation or in the future maybe a Cuda system or a server with Tesla cards. I work with OdT everyday but I want also to teach in class and convincing my Uni  to buy 20 quadro cards is not easy (So far I have 10 which is good).

I have performed several tests and from an old Dell laptop with a Quadro and Ubuntu installed I can connect on my workstation and it works perfectly fine through SSH.

Then I tried from a windows 8 laptop with a regular mobile NVidia + the intel chipset. Using Putty and Xming. I can do everything I want except indirect rendering. I spent some time reading about the error code (Xlib is missing the extension NV-GLX). And apparently it is due to the difference in architecture between the systems. There are compatibility flags and if the X server is not happy then you switch from indirect rendering to direct rendering (which is catastrophic over the network indeed). Then I went to see how to update my server in case it would perform better. And I discovered the numerous flavours of mesa and I must admit I don't know what to choose (I have by default installed mesa-dri).
Here a link to the description of the problem
http://www.linuxquestions.org/questions/linux-software-2/remote-3d-is-it-possible-839699/
I have also noticed the presence of a od_glxinfo program which might be some of the solution.

My investigation might seems confused and I would be please to have your advices on that. Particularly if you found a turnaround (knowing that I am not a huge fan of remote control of the machine through vnc).

Thank you in advance,

Julien

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendtect.org/pipermail/developers/attachments/20130226/e53f8ec7/attachment.html>