F5F Stay Refreshed Power Users Networks VNC Woes

VNC Woes

VNC Woes

M
megapixel74
Member
224
08-14-2016, 11:21 AM
#1
I own a Mac Mini from mid-2012 with a Core i5 processor and 8GB RAM, which I use as a development server. I often connect to the desktop via built-in-to-macOS VNC services so I can run tools like Xcode. My setup runs on a Windows 10 machine (version 1809, build 17763.914) using RealVNC's VNC Viewer. I’m connecting through a 1Gbit NIC on the Windows side (Intel I219-V chipset) and a 1Gbit NIC on the Mac Mini (Broadcom BCM57765), all routed through an HPE 2915 switch. Both devices are on the same VLAN, and the connection shows full-duplex at 1000baseT. A CrystalDiskMark 7 test confirms I can fully utilize the gigabit link between them. The problem is that VNC services are stuck at 100Mbit/s maximum, which limits the experience despite being functional. I’m not running heavy computational tasks—just using text editors. I’ve tried various fixes: adjusting color settings, tweaking Windows VNC data rates, changing quality options, resetting network settings, and even switching to jumbo packets (9000 MTU vs 1500). Still, the throughput remains constrained. Online searches often point to older forums (Windows XP, Mac OS X 10.5), but my scenario is quite different. I’m certain I need a wired connection—my wireless setup would be poor—and ideally rely on an edge switch or a crossover cable with auto MDI-X adapter. No matter the setup, VNC appears limited to fast Ethernet speeds. What advice would you all give?
M
megapixel74
08-14-2016, 11:21 AM #1

I own a Mac Mini from mid-2012 with a Core i5 processor and 8GB RAM, which I use as a development server. I often connect to the desktop via built-in-to-macOS VNC services so I can run tools like Xcode. My setup runs on a Windows 10 machine (version 1809, build 17763.914) using RealVNC's VNC Viewer. I’m connecting through a 1Gbit NIC on the Windows side (Intel I219-V chipset) and a 1Gbit NIC on the Mac Mini (Broadcom BCM57765), all routed through an HPE 2915 switch. Both devices are on the same VLAN, and the connection shows full-duplex at 1000baseT. A CrystalDiskMark 7 test confirms I can fully utilize the gigabit link between them. The problem is that VNC services are stuck at 100Mbit/s maximum, which limits the experience despite being functional. I’m not running heavy computational tasks—just using text editors. I’ve tried various fixes: adjusting color settings, tweaking Windows VNC data rates, changing quality options, resetting network settings, and even switching to jumbo packets (9000 MTU vs 1500). Still, the throughput remains constrained. Online searches often point to older forums (Windows XP, Mac OS X 10.5), but my scenario is quite different. I’m certain I need a wired connection—my wireless setup would be poor—and ideally rely on an edge switch or a crossover cable with auto MDI-X adapter. No matter the setup, VNC appears limited to fast Ethernet speeds. What advice would you all give?

R
redman81
Member
72
08-16-2016, 01:51 PM
#2
Should this be true it wouldn't be the only issue. VNC Viewer to my knowledge does not use GPU acceleration. It renders off the CPU. This will make for a poor choppy desktop experience. For a lot of server applications as a management tool it's fine but a daily driver it'd be miserable. Look into something like PARSEC . It requires that the "server" have a GPU. It will use the GPU for rendering the desktop then copy the GPU's frame buffer over the network to your client. Makes for a snappy/responsive experience. Weather or not they support MacOS I can't say but it's something you can checkout.
R
redman81
08-16-2016, 01:51 PM #2

Should this be true it wouldn't be the only issue. VNC Viewer to my knowledge does not use GPU acceleration. It renders off the CPU. This will make for a poor choppy desktop experience. For a lot of server applications as a management tool it's fine but a daily driver it'd be miserable. Look into something like PARSEC . It requires that the "server" have a GPU. It will use the GPU for rendering the desktop then copy the GPU's frame buffer over the network to your client. Makes for a snappy/responsive experience. Weather or not they support MacOS I can't say but it's something you can checkout.