NX client is another way to graphically connect to the Linux servers. The Linux server runs RHEL 7.3 (virtual machine, KDE). Cadence, Matlab and Altera Quartus either did not work or were exceptionally slow. Windows desktop accessed through WRD runs Windows 7. I recommend using the fit to window option and re-size your window to the correct size. NoMachine has a number of display settings you can choose. I am currently trying to use a Jetson Nano Ubuntu 18.04 without a monitor by using NoMachine software but it consumes a lot of processing power (approximately 20-30 of each CPU core) and causes my deep learning model predictions to slow down when I want to see the output on the screen. Connecting/disconnecting a few times through WRD to the desktop often helps to make NoMachine to work much faster.Ĭould you please let me know if there is anything I could do to improve performance of NoMachine when it is used through WRD? Most of the linux desktops in the University have the screen dimensions of 2560x1080 so matching this may be problematic on a local machine with smaller screen sizes. In both cases, I can feel slowdown of NoMachine if it is used through WRD. I use setup 2) both to work from home and to connect from one desktop at work to another (the two desktops are in close proximity). By slow, I mean that: A) it could take seconds for the Linux server screen to refresh, B) responsiveness of the Windows desktop accessed through WRD is much higher than of the server accessed through NoMachine from the desktop. In setup 1) NoMachine works very fast, in setup 2) it often works quite slow.
1) A Windows desktop connects to a Linux server using NoMachine.Ģ) A Windows desktop connects to another Windows desktop through Windows Remote Desktop ( WRD) and then from there connects to a Linux server using NoMachine.
0 kommentar(er)
