Raspberry Pi as x2go “thin” client
multi-seat.com
multi-seat.com
I'm not surprised a raspi can do that, as I've used an antique thinkpad x201 for doing it for many many years now!
I can develop using geany/vscode/eclipse remotely over a reasonably good DSL/fibre connection and quite frankly, there is zero difference with being "local" to the workstation. Don't even need a LAN.
Only thing which obviously doesn't work as good is web browsing/video etc as that is inherently a lot more pixel pushing.
I kinda worry about the economical likely next steps of using a thin client like a raspberry pi, like everything will become netflix/stadia and you never own the important bits.
But on the technical side it’s really great.
The raspberry pi is a competent little computer and probably way more capable than those “sun” ray thin clients
The Sun Rays had also decent sound ("CD quality"), a Cisco compatible VPN client and a smart card which allowed one to comfortably drag one's session from one Ray to another (home to office, cubicle to lab, etc.).
I tried using xrdp before, but, at least at the time I tried it a few years back, personally felt I got better performance with nomachine vs. xrdp, although perhaps this has changed now. I've tried x2go with individual applications before, but never the entire desktop, perhaps I'll have to give that a try sometime.
Would love to hear more experiences of others who remote this way where you are “offloading” your compute power elsewhere.
I experience the performance issues on the LAN, for instance, even with a 1,300mbps negotiated connection.
We also have an R720 at work, running a Windows Server 2016 under Hyper-V and it performs very poorly (Windows UI is super slow, etc.). I know next to nothing about physical servers, but I've had great success swapping HDDs for SSDs in laptops to dramatically increase Windows' modern UI's performance. Our R720 has HDDs instead of SSDs, I've thought of upgrading them to see how it works out.
If you ever find a solution, please let me know.
Windows performance on this machine is atrocious (virtualized in ESXI) whereas Linux is great.
RDP is still only limited to 30 FPS for whatever reason and so you may continue to be disappointed in it.
Also 1,300 Mbps sounds like a wireless network so your main problem on the network side is being half duplex and airtime delays (even from just beacons) not throughput. I'd pick a 100 Mbps hardwire to RDP on over any Wi-Fi setup as the video bandwidth isn't actually that helpful but jitter/latency are problems with trying to send inputs at the same time. Not much you can do about that though.
https://admx.help/?Category=Windows_10_2016&Policy=Microsoft...
https://admx.help/?Category=Windows_10_2016&Policy=Microsoft...
https://admx.help/?Category=Windows_10_2016&Policy=Microsoft...
The 2 you need to enable to just enable RemoteFX are "Use hardware graphics adapters for all Remote Desktop Service sessions" to Enabled and "RemoteFX for Windows Server 2008 R2/Configure RemoteFX" to "Enabled". These 2 should net you GPU acceleration in the remote session.
For GPU accelerated encoding you can also set "Configure H.264/AVC hardware encoding for Remote Desktop Connections" to "Enabled".
Those 3 policies are all I usually tick but the rest of the policies in that tree are nerd knob tunables with many relating to bandwidth/resource utilization/image quality tradeoffs if that so interests you.
I’m generally using office, internet, Windows terminals/ssh, IDEs etc. Very rarely an overly dramatic full page video advert will jolt me back to reality that I’m doing this over RDP.
Use a wired 1Gbps connection. If it works acceptably -- which it has in every single setting I've tried -- then it is your network, though it might not be where you usually look (e.g. speedtest measures your overall bandwidth, but if you have many retransmits, you might have horrible interactive experience even with sufficient bandwidth).
It might be frantically trying to look at every packet flying by.
In fact just yesterday while I could easily connect with RDP, Slack was just dying when trying to share screens.
Moonlight is open-source, you can see in the code yourself as I don't understand most of it. There is also a project that attempt to replace the associated Nvidia Gamestream server but it is quite basic and no longer maintained : https://github.com/loki-47-6F-64/sunshine
I'd also check your choice of RDP client -- are you using the official Microsoft client or a FOSS one? I believe there are extensions to RDP that basically wrap H.264, which you'd probably want at that resolution.
Although one should also mention that the Pis are a little too slow for „serious“ work, and x2go can be buggy.
Hopefully this “just works” now on a raspberry pi 4 and newer raspbian, but I haven’t checked.
The license is cheap and it works in multi-monitor mode as well[2].
[1]:https://tls.thinlinx.com/store/index.php/thinclient/tlxos-rp... [2]:https://www.youtube.com/watch?v=rsob_pQXnCM
Ordered it.
it just has to be updated whenever windows gets a new update, lets say every 6 months or so, im not sure
other than that, i have never used linux as a "server" but i guess the performance would be equally good.
> The website is temporarily unable to service your request as it exceeded resource limit. Please try again later.
F