Forum / NoMachine Terminal Server Products / Evaluation questions / Reply To: Evaluation questions
How effective is the hardware encoding on a Linux Terminal Server? If we use an Nvidia card in our Terminal server how many virtual desktops will benefit from hardware accelerated encoding? I assume there is a limit on the number of simultaneous streams that can be encoded on the card (8?). Is hardware encoding supported for VP8 or is it a h264 feature only? The Terminal Server evaluation lacks h264 support.
We don’t use hardware encoders. We use the hardware only on decoding side.
The seamless/rootless mode for running a single application seems to garble quite a lot of the graphics (e.g. the mouse pointer) and the performance of the graphics updates suffers (e.g. playing video) when compared to running the same application in a full desktop. Is this a known limitation? I am running an EL6 server/client.
Full desktop sessions can work either via the NX compression of X protocol (“lightweight” mode) or via H.264/VP8 encoding. Rootless sessions always work through a mix of compressed X protocol and VP8 encoding. This is not a limitation on performance generally, but there could be some difference under specific conditions and with specific applications.
Can the options in the !M tray icon be customised? For example if I disable the whiteboard in the node.cfg it still appears in the icon drop down menu (but does nothing). It’s the same for allowing uploads, if disabled it still appears in the icon dropdown. I’d be happy if the icon only gave the option to record the session or “download a file from the server” and nothing more.
In fact those unavailable items should not be visible. We’ve recently noticed the problem, a fix is ready and will be released soon.
Can the option to show the menu panel also be completely disabled? We don’t want users to be able to play with settings or try to create new connections.
We’re planning to implement this feature that may help you:
It is still not approved because we want to be sure to offer a flexible solution. For example in your case the ‘Disabled’ setting may not be correct because you don’t want to forbid the credential saving but just disable the menu panel.
[VGL] ERROR: Could not open display :0.
The X server is running on :0 using the nvidia module. Maybe it’s an auth issue? This is on EL6.
This is due to a failure connecting to the 3D X server. I suggest running again the vglserver_config script by adding command line options: +s +f +t.
Am I correct in assuming that VGL uses the graphic card in a Terminal Server to draw the GL which is then video encoded in the normal NX way and sent to the client? Could the VGL be sent and drawn on the connecting client instead? All our desktop clients have fast graphics cards so can we u utilise them to improve the display quality/speed? Does hardware decoding (h264) make a big difference to the desktop experience?
Our software uses VirtualGL to render OpenGL application in hardware on the server side. We don’t provide a channel forwarding OpenGL calls or GLX requests to the client side.