Re: [VirtualGL-Users] Performances problem, I need some help :)
3D Without Boundaries
Brought to you by:
dcommander
From: DRC <dco...@us...> - 2010-09-22 21:57:50
|
You have to run vglserver_config on machine_B in order to grant access to the 3D X display while it is sitting at the login prompt. This is in the User's Guide. You should never set VGL_DISPLAY to $DISPLAY. That will cause VirtualGL to ship the 3D rendering commands to the client machine, then send back uncompressed rendered images to the server machine, then send back compressed rendered images to the client machine. This somewhat defeats the purpose of using VirtualGL, since VGL is designed to perform server-side 3D rendering and thus avoid the transmission of OpenGL commands over the network. On 9/22/10 10:54 AM, Philippe wrote: > Some times passed from my previous mail, but I just right now try > VirtualGL 2.2beta and discover a thing I never take care before : > I must launch a user session on my Ubuntu VirtualGL server to be able to > render from the server's graphic cards. > > For example : > machine_A is the client. > machine_B is the server. > > machine_A > vglconnect user@machine_B > machine_B (with an open user session) > vglrun my_application > > Result : > [VGL] NOTICE: Automatically setting VGL_CLIENT environment variable to > [VGL] 172.17.40.17, the IP address of your SSh client. > Polygons in scene: 62464 > Visual ID of window: 0x21 > OpenGL Renderer: GeForce GTX 295/PCI/SSE2 > > That's OK, the rendering is on the GTX 295 and the display is watchable > on the screen of machine_A > > Now : > machine_A > vglconnect user@machine_B > machine_B (on login screen) > vglrun my_application > > Result : > [VGL] NOTICE: Automatically setting VGL_CLIENT environment variable to > [VGL] 172.17.40.17, the IP address of your SSh client. > Polygons in scene: 62464 > No protocol specified > [VGL] ERROR: Could not open display :0. > > So it warns me he can't open the display on the screen of machine_B. > > Then I tried this : > machine_A > vglconnect user@machine_B > machine_B (on login screen) > vglrun -d $DISPLAY my_application > > Result : > [VGL] NOTICE: Automatically setting VGL_CLIENT environment variable to > [VGL] 172.17.40.17, the IP address of your SSh client. > Polygons in scene: 62464 > Visual ID of window: 0x21 > [VGL] WARNING: The OpenGL rendering context obtained on X display > [VGL] localhost:10.0 is indirect, which may cause performance to suffer. > [VGL] If localhost:10.0 is a local X display, then the framebuffer device > [VGL] permissions may be set incorrectly. > OpenGL Renderer: GeForce Go 7300/PCI/SSE2 > > It does the render, but on the machine_A graphic card. > > > > Then, I don't understand how to render without any user connected to > machine_B. > > Thanks for you help guys. > On Tue, Jun 22, 2010 at 7:29 PM, DRC <dco...@us... > <mailto:dco...@us...>> wrote: > > Note the warning about the OpenGL rendering context. That is the > problem here. It appears you are overriding the value of VGL_DISPLAY. > Why are you doing this? VGL_DISPLAY should always be set to the display > where you want the 3D rendering to occur, which in this case is the X > display where the GTX295 is connected. If it is connected to :0.0, then > unset VGL_DISPLAY, because :0.0 is the default value of that variable. > > The User's Guide explains this in great detail. > > On 6/22/10 4:10 AM, Philippe wrote: > > Thanks for the reply, > > Contexts of the tests : > > - Server : Ubuntu 9.04 32b / VirtualGL 2.1.4 / QuadSLI GTX295 with > > nvidia's drivers version 195.36.24 > > - Client : Ubuntu 10.04 64b / VirtualGL 2.1.4 / Nvidia 7600GT with > > nvidia's drivers version 195.36.24 > > - 100mb network first time, Gb network 2nd time. > > > > here are the logs : > > > > 100mb network : > > > > didier@LDC-T:~$ /opt/VirtualGL/bin/vglrun -sp +pr > /opt/VirtualGL/bin/glxspheres > > [VGL] NOTICE: Automatically setting VGL_CLIENT environment variable to > > > > [VGL] 172.17.40.4, the IP address of your SSh client. > > Polygons in scene: 62464 > > Visual ID of window: 0x21 > > [VGL] WARNING: The OpenGL rendering context obtained on X display > > [VGL] localhost:11.0 is indirect, which may cause performance to > suffer. > > > > [VGL] If localhost:11.0 is a local X display, then the > framebuffer device > > [VGL] permissions may be set incorrectly. > > Readback - 3.32 Mpixels/sec- 2.98 fps > > 1.427887 frames/sec - 1.593522 Mpixels/sec > > > > Compress 0 - 51.81 Mpixels/sec- 46.42 fps > > Total - 1.59 Mpixels/sec- 1.43 fps- 2.36 Mbits/sec > (16.2:1) > > Readback - 3.33 Mpixels/sec- 2.99 fps > > 1.431452 frames/sec - 1.597501 Mpixels/sec > > > > Compress 0 - 50.12 Mpixels/sec- 44.91 fps > > Total - 1.60 Mpixels/sec- 1.43 fps- 2.57 Mbits/sec > (14.9:1) > > Readback - 3.38 Mpixels/sec- 3.03 fps > > 1.449498 frames/sec - 1.617640 Mpixels/sec > > > > Compress 0 - 45.18 Mpixels/sec- 40.49 fps > > Total - 1.61 Mpixels/sec- 1.45 fps- 2.73 Mbits/sec > (14.2:1) > > Readback - 3.45 Mpixels/sec- 3.09 fps > > 1.459527 frames/sec - 1.628832 Mpixels/sec > > > > Compress 0 - 43.29 Mpixels/sec- 38.79 fps > > Total - 1.63 Mpixels/sec- 1.46 fps- 2.79 Mbits/sec > (14.0:1) > > Readback - 3.32 Mpixels/sec- 2.98 fps > > 1.437647 frames/sec - 1.604414 Mpixels/sec > > > > Compress 0 - 43.10 Mpixels/sec- 38.62 fps > > Total - 1.60 Mpixels/sec- 1.44 fps- 2.79 Mbits/sec > (13.8:1) > > Readback - 3.32 Mpixels/sec- 2.97 fps > > 1.433601 frames/sec - 1.599898 Mpixels/sec > > > > Compress 0 - 43.07 Mpixels/sec- 38.59 fps > > Total - 1.60 Mpixels/sec- 1.43 fps- 2.78 Mbits/sec > (13.8:1) > > Readback - 3.45 Mpixels/sec- 3.09 fps > > 1.466370 frames/sec - 1.636468 Mpixels/sec > > > > Compress 0 - 42.36 Mpixels/sec- 37.95 fps > > Total - 1.64 Mpixels/sec- 1.47 fps- 2.83 Mbits/sec > (13.9:1) > > Readback - 3.46 Mpixels/sec- 3.10 fps > > 1.462891 frames/sec - 1.632586 Mpixels/sec > > > > Compress 0 - 43.28 Mpixels/sec- 38.78 fps > > Total - 1.64 Mpixels/sec- 1.47 fps- 2.83 Mbits/sec > (13.8:1) > > Readback - 3.46 Mpixels/sec- 3.10 fps > > 1.465122 frames/sec - 1.635076 Mpixels/sec > > > > Compress 0 - 44.43 Mpixels/sec- 39.81 fps > > Total - 1.63 Mpixels/sec- 1.46 fps- 2.83 Mbits/sec > (13.8:1) > > Readback - 3.46 Mpixels/sec- 3.10 fps > > 1.461738 frames/sec - 1.631300 Mpixels/sec > > > > Compress 0 - 47.80 Mpixels/sec- 42.84 fps > > Total - 1.63 Mpixels/sec- 1.46 fps- 2.83 Mbits/sec > (13.8:1) > > Readback - 3.47 Mpixels/sec- 3.11 fps > > 1.466228 frames/sec - 1.636310 Mpixels/sec > > > > Compress 0 - 43.15 Mpixels/sec- 38.66 fps > > Total - 1.64 Mpixels/sec- 1.47 fps- 2.82 Mbits/sec > (13.9:1) > > Readback - 3.46 Mpixels/sec- 3.10 fps > > 1.464902 frames/sec - 1.634831 Mpixels/sec > > > > Compress 0 - 43.21 Mpixels/sec- 38.71 fps > > Total - 1.63 Mpixels/sec- 1.46 fps- 2.82 Mbits/sec > (13.9:1) > > Readback - 3.46 Mpixels/sec- 3.10 fps > > 1.466725 frames/sec - 1.636865 Mpixels/sec > > > > Compress 0 - 45.26 Mpixels/sec- 40.56 fps > > Total - 1.64 Mpixels/sec- 1.47 fps- 2.81 Mbits/sec > (14.0:1) > > Readback - 3.46 Mpixels/sec- 3.10 fps > > > > > > > > > > > > On Gb network : > > > > didier@LDC-T:~$ /opt/VirtualGL/bin/vglrun -sp +pr > /opt/VirtualGL/bin/glxspheres > > Polygons in scene: 62464 > > Visual ID of window: 0x21 > > [VGL] WARNING: The OpenGL rendering context obtained on X display > > [VGL] 172.17.40.4:0.0 is indirect, which may cause performance > to suffer. > > > > [VGL] If 172.17.40.4:0.0 is a local X display, then the > framebuffer device > > [VGL] permissions may be set incorrectly. > > Readback - 28.51 Mpixels/sec- 25.54 fps > > 2.687975 frames/sec - 2.999780 Mpixels/sec > > > > Compress 0 - 51.58 Mpixels/sec- 46.22 fps > > Total - 3.00 Mpixels/sec- 2.69 fps- 4.61 Mbits/sec > (15.6:1) > > > > Readback - 23.91 Mpixels/sec- 21.42 fps > > > > 2.479951 frames/sec - 2.767626 Mpixels/sec > > > > > > Compress 0 - 48.86 Mpixels/sec- 43.78 fps > > > > Total - 2.76 Mpixels/sec- 2.47 fps- 4.68 Mbits/sec > (14.2:1) > > > > Readback - 29.71 Mpixels/sec- 26.62 fps > > > > 2.528143 frames/sec - 2.821408 Mpixels/sec > > > > > > Compress 0 - 55.23 Mpixels/sec- 49.49 fps > > > > Total - 2.84 Mpixels/sec- 2.54 fps- 4.91 Mbits/sec > (13.9:1) > > > > Readback - 29.26 Mpixels/sec- 26.22 fps > > > > 2.674947 frames/sec - 2.985241 Mpixels/sec > > > > > > Compress 0 - 45.22 Mpixels/sec- 40.52 fps > > > > Total - 2.97 Mpixels/sec- 2.66 fps- 5.12 Mbits/sec > (13.9:1) > > > > Readback - 28.96 Mpixels/sec- 25.95 fps > > > > 2.642373 frames/sec - 2.948889 Mpixels/sec > > > > > > Compress 0 - 42.33 Mpixels/sec- 37.93 fps > > > > Total - 2.95 Mpixels/sec- 2.64 fps- 5.10 Mbits/sec > (13.9:1) > > > > Readback - 29.03 Mpixels/sec- 26.01 fps > > 2.608035 frames/sec - 2.910567 Mpixels/sec > > > > Compress 0 - 42.37 Mpixels/sec- 37.96 fps > > Total - 2.91 Mpixels/sec- 2.61 fps- 5.01 Mbits/sec > (14.0:1) > > Readback - 29.30 Mpixels/sec- 26.26 fps > > 2.643140 frames/sec - 2.949745 Mpixels/sec > > > > Compress 0 - 45.36 Mpixels/sec- 40.65 fps > > Total - 2.95 Mpixels/sec- 2.64 fps- 5.05 Mbits/sec > (14.0:1) > > Readback - 29.12 Mpixels/sec- 26.09 fps > > 2.698202 frames/sec - 3.011193 Mpixels/sec > > > > Compress 0 - 42.85 Mpixels/sec- 38.39 fps > > Total - 3.00 Mpixels/sec- 2.69 fps- 5.14 Mbits/sec > (14.0:1) > > Readback - 29.68 Mpixels/sec- 26.59 fps > > 2.658916 frames/sec - 2.967350 Mpixels/sec > > > > Compress 0 - 43.54 Mpixels/sec- 39.01 fps > > Total - 2.98 Mpixels/sec- 2.67 fps- 4.77 Mbits/sec > (15.0:1) > > Readback - 29.42 Mpixels/sec- 26.36 fps > > 2.585393 frames/sec - 2.885299 Mpixels/sec > > > > > > > > > > And if I launch glxspheres just with ssh -X : > > 389.248438 frames/sec - 434.401256 Mpixels/sec > > 379.393107 frames/sec - 423.402707 Mpixels/sec > > 375.535425 frames/sec - 419.097534 Mpixels/sec > > 371.433732 frames/sec - 414.520044 Mpixels/sec > > 375.291968 frames/sec - 418.825837 Mpixels/sec > > 379.474747 frames/sec - 423.493817 Mpixels/sec > > 372.979736 frames/sec - 416.245385 Mpixels/sec > > 372.818163 frames/sec - 416.065070 Mpixels/sec > > > > > > So, Houston, I got a problem :) > > > > Thanks for your help. > > > > Philippe. > > > > > > On Tue, Jun 22, 2010 at 7:10 AM, DRC > <dco...@us... > <mailto:dco...@us...> > > <mailto:dco...@us... > <mailto:dco...@us...>>> wrote: > > > > -- Kill all instances of vglclient on the client machine. > > > > -- Ensure that the client is using 1280x1024 or higher resolution > > > > -- export VGL_PROFILE=1 on the client machine > > > > -- vglconnect user@server > > > > -- Launch > > > > vglrun -sp +pr /opt/VirtualGL/bin/glxspheres > > > > on the server > > > > -- Let it run for 60 seconds or so, then kill it > > > > -- Post the output from the server console as well as the > contents of > > ~/.vgl/vglconnect-{client}-:0.0.log from the client machine > > > > On 6/21/10 8:29 AM, Philippe wrote: > > > Hello, > > > I was using VirtualGL 2.1.2 successfully on a core i7 with a Quad > > SLI of > > > GTX295 and Ubuntu 9.04 64b. > > > I change the Ubuntu for a 32b version, upgrade sometimes nvidia > > drivers > > > and re-use VirtualGL, with the last version : 2.1.4 (and > tried with > > > 2.1.3), and I got a big problem with the performances. > > > > > > For example if I launch glxgears just with a simple remote > display > > (ssh > > > -X), I got more than 5400FPS, and if I connect my computer with > > > vglconnect user@machine and I launch glxgears with vglrun, I > got 8 > > FPS ... > > > > > > I will soon reinstall the machine under Ubuntu 10.04 64b, but > this > > "bug" > > > is a very problem, so maybe anyone can have an idea if it's > VGL or the > > > Nvidia's drivers ? > > > > > > Thanks ! > > > > > > Philippe > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > ThinkGeek and WIRED's GeekDad team up for the Ultimate > > > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > > > lucky parental unit. See the prize list and enter to win: > > > http://p.sf.net/sfu/thinkgeek-promo > > > > > > > > > > > > _______________________________________________ > > > VirtualGL-Users mailing list > > > Vir...@li... > <mailto:Vir...@li...> > > <mailto:Vir...@li... > <mailto:Vir...@li...>> > > > https://lists.sourceforge.net/lists/listinfo/virtualgl-users > > > > > ------------------------------------------------------------------------------ > > ThinkGeek and WIRED's GeekDad team up for the Ultimate > > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > > lucky parental unit. See the prize list and enter to win: > > http://p.sf.net/sfu/thinkgeek-promo > > _______________________________________________ > > VirtualGL-Users mailing list > > Vir...@li... > <mailto:Vir...@li...> > > <mailto:Vir...@li... > <mailto:Vir...@li...>> > > https://lists.sourceforge.net/lists/listinfo/virtualgl-users > > > > > > > > > > ------------------------------------------------------------------------------ > > ThinkGeek and WIRED's GeekDad team up for the Ultimate > > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > > lucky parental unit. See the prize list and enter to win: > > http://p.sf.net/sfu/thinkgeek-promo > > > > > > > > _______________________________________________ > > VirtualGL-Users mailing list > > Vir...@li... > <mailto:Vir...@li...> > > https://lists.sourceforge.net/lists/listinfo/virtualgl-users > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > VirtualGL-Users mailing list > Vir...@li... > <mailto:Vir...@li...> > https://lists.sourceforge.net/lists/listinfo/virtualgl-users > > > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > > > > _______________________________________________ > VirtualGL-Users mailing list > Vir...@li... > https://lists.sourceforge.net/lists/listinfo/virtualgl-users |