Getting exactly 1 FPS on vglrun glxgears/glxspheres

[ziegler]

I have set up VirtualGL to run OpenGL applications on an Nvidia card through TurboVNC.

I run lightdm display manager, and a mate-session.

Based on what glxinfo tells me, the setup seems to be working:

"OpenGL vendor string: NVIDIA Corporation

OpenGL renderer string: GeForce GTX 1650/PCIe/SSE2

OpenGL core profile version string: 4.6.0 NVIDIA 440.26"

I now have the strange effect that basically any application (I have tried glxgears, glxspheres and my own custom code) that I run through vglrun runs with exactly 1.00 FPS (check the screenshot below).

The CPU usage while running is negligible, so I assume that there is some artificial throttling happening, like some bogus VSYNC.

One thing special maybe about my setup is that this is a rack mount server, which, appart from the discrete Nvidia card, also has an onboard VGA which runs GL via mesa, so this is a dual head setup.

I separately tried

VGL_SPOILLAST=0

VLS_SYNC=1

With no noticeable effect.

Has anybody experienced this strange effect? Any ideas on how to solve it?

Any hint is appreciated, Thanks!

Julius

[Julius Ziegler]

For now, I solved the issue by downgrading from the very new nvidia 440 driver to version 435.

 

Regards

Julius

 

--
You received this message because you are subscribed to the Google Groups "VirtualGL User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to virtualgl-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/f5e8e998-89bd-4bfc-8022-d08813934c0c%40googlegroups.com.

 

[DRC]

Good, because I have no clue why that issue would occur. Even if VGL_FPS was set, it would still be necessary to disable frame spoiling in order for benchmarks to reflect that frame rate. It definitely does seem like a driver issue.

On Oct 19, 2019, at 4:27 AM, Julius Ziegler <zie...@atlatec.de> wrote:

For now, I solved the issue by downgrading from the very new nvidia 440 driver to version 435.

 

Regards

Julius

 

 

From: ziegler
Sent: Saturday, 19 October 2019 10:47
To: VirtualGL User Discussion/Support
Subject: [VirtualGL-Users] Getting exactly 1 FPS on vglrun glxgears/glxspheres

 

I have set up VirtualGL to run OpenGL applications on an Nvidia card through TurboVNC.

 

I run lightdm display manager, and a mate-session.

 

Based on what glxinfo tells me, the setup seems to be working:

 

"OpenGL vendor string: NVIDIA Corporation

OpenGL renderer string: GeForce GTX 1650/PCIe/SSE2

OpenGL core profile version string: 4.6.0 NVIDIA 440.26"

 

I now have the strange effect that basically any application (I have tried glxgears, glxspheres and my own custom code) that I run through vglrun runs with exactly 1.00 FPS (check the screenshot below).

 

The CPU usage while running is negligible, so I assume that there is some artificial throttling happening, like some bogus VSYNC.

 

One thing special maybe about my setup is that this is a rack mount server, which, appart from the discrete Nvidia card, also has an onboard VGA which runs GL via mesa, so this is a dual head setup.

 

I separately tried

 

VGL_SPOILLAST=0

VLS_SYNC=1

 

With no noticeable effect.

 

Has anybody experienced this strange effect? Any ideas on how to solve it?

 

Any hint is appreciated, Thanks!

 

Julius

 

<AAEAE6044B9641D1B9DE056EDF9F4367.png>

[BjörnS]

Hi all,

I ran into the same issue. The FPS drops to 1 after the the screen lock kicks in, i.e. after the number of minutes when the the screen locks. This happens since the update to nvidia 440.31. System is centos 7.  GFX card is GeForce GTX 1080 Ti. The effect does not show in identical system with GeForce RTX 2080.

Any help on how to resolve this is very welcome.

[DRC]

VirtualGL is designed to be used with a dedicated 3D X server, i.e. with a GPU-attached X server that is not logged in or otherwise doing anything not related to VirtualGL.  Are you saying that the 3D X server is logged in and this issue occurs when the screen saver activates on it?  If so, then that is not an issue we can solve.

--
You received this message because you are subscribed to the Google Groups "VirtualGL User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to virtualgl-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/b2510075-18c5-4d1a-9241-fe7befcbb6e3%40googlegroups.com.

[bjse...@gmail.com]

Thx for the reply.

It's a dedicated 3D X server.

I only verified the link to the screen lock by logging on both locally and remotely, have glxsgears run remotely (vglconnect, vglrun glxgears) and observe the drop in fps.

The drop also occured without being logged on locally.

I tend to believe the issue is due to the nvidia driver rather than virtualgl

To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/7d990830-2a68-eef6-3328-42284bc1ef1f%40virtualgl.org.

[praines]

I just upgraded over 50 Linux workstations to NVIDIA driver 440 from 418 and now all vglrun apps in VNC and NoMachine are running at ~1 fps

Definitely something to do with the latest NVIDIA driver

[Patrik Pira]

From the changelog for 440.26:

- Enabled HardDPMS by default. See the README entry on the X configuration
      option "HardDPMS" for more information.

Try,

Option "HardDPMS" "false"

[Richard Ems]

This solved the issue for me on CentOS 7.7 with NVIDIA 440.36 and VirtualGL 2.6.3.

Thanks Patrik !

[DRC]

I’m curious as to whether configuring the X server to be headless would also work around this.

--
You received this message because you are subscribed to the Google Groups "VirtualGL User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to virtualgl-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/2b42aeff-185b-465d-88a3-0ed223664257%40googlegroups.com.

[Patrik Pira]

If you by headless mean "--use-display-device=None" then no, it does not workaround this.

To unsubscribe from this group and stop receiving emails from it, send an email to virtual...@googlegroups.com.

[Rangesh Gupta]

We also faced a similar issue. We are able to fix it without downgrading the driver. Below changes we did:

1. Added "consoleblank=0" to the end of GRUB_CMDLINE_LINUX in /etc/default/grub, then ran the grub2-mkconfig 
2. Set usedisplaydevice none in the /etc/X11/xorg.conf
3. In /etc/X11/xorg.conf, Commented out all 'Option "DPMS"' lines and added Option "dpms" "false"

Section "ServerFlags"

Option "BlankTime" "0"

Option "StandbyTime" "0"

Option "SuspendTime" "0"

Option "OffTime" "0"

Option "dpms" "false"

EndSection 

To unsubscribe from this group and stop receiving emails from it, send an email to virtual...@googlegroups.com.

[Patrik Pira]

Looks like the Nvidia driver version 440.59 might be fixed now. I have not tried it though.

From the releasenotes:

- Disabled frame rate limiting for configurations without active displays when HardDPMS is enabled.

--
You received this message because you are subscribed to the Google Groups "VirtualGL User Discussion/Support" group.

To unsubscribe from this group and stop receiving emails from it, send an email to virtualgl-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/08d89bf7-e24a-4969-9f51-53f8150d0e65%40googlegroups.com.

[Eric Frey]

I was having the same issue with version 450.66 on a CentOS 7 system. Commenting out Option "DPMS" in the monitor section and adding Option "hardpms" "false" as suggested by Patrik Pira fixed the problem. Many thanks for the posts.

[Eric Frey]

One more thing: to get it to work without a monitor connected I added 

Option "AllowEmptyInitialConfiguration" "true"

to the Device section.

[DRC]

Yes, the Headless nVidia Mini How-To covers both issues:

https://virtualgl.org/Documentation/HeadlessNV

But it should be noted that the DPMS issue exists irrespective of whether the GPU is headless.

On Aug 29, 2020, at 1:49 PM, Eric Frey <ecf...@gmail.com> wrote:

One more thing: to get it to work without a monitor connected I added 

To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/b68c8c3d-c151-4c75-b956-d2722194cb22n%40googlegroups.com.