Engineering Sub-15ms Input Latency: SendInput, TCP_NODELAY & Zero-Copy Framing
Why do some remote desktop sessions feel sluggish even on a gigabit fiber connection? The culprit is rarely network bandwidth — it is Nagle buffering, user-mode message queue delays, and synchronous frame encoding.
Eliminating Nagle's Algorithm with TCP_NODELAY
| Metric | SimpleViewer 2.3 | AnyDesk 8.x | TeamViewer 15.x |
|---|---|---|---|
| Median Relay Frame Latency | 11.4 ms (60 FPS) | 16.8 ms | 23.5 ms |
| Cold-Start Connection Time | 1.2 s | 2.1 s | 3.8 s |
| Idle Background RAM | 24 MB | 68 MB | 145 MB |
| Free Unattended PCs | 3 PCs (No Timeouts) | Flagged / Restricted | 60-sec Commercial Block |
Hardware Scancode Injection via Win32 SendInput
Instead of posting synthetic window messages that fail in elevated UAC windows or 3D viewports, SimpleViewer injects hardware scancodes and normalized 16-bit absolute mouse coordinates directly into the kernel input stream.
Backpressure-Aware Frame Pacing
By monitoring socket send-queue depth on port 7891, the host encoder never queues stale frames behind congested packets, keeping mouse and keyboard feedback instantaneous.
Related Engineering Articles
Top 5 TeamViewer & AnyDesk Alternatives in 2026 (No Commercial Use Blocks)
Tired of 60-second 'Commercial use suspected' disconnects and €300/yr renewals? Compare SimpleViewer, RustDesk, Jum...
SimpleViewer vs. AnyDesk vs. TeamViewer: 2026 Security & Latency Benchmark
Reproducible 2026 performance benchmarks comparing SimpleViewer 2.3 against AnyDesk, TeamViewer, and Jump Desktop a...
Mastering Multi-Monitor 60 FPS Remote Desktop & WASAPI Audio Streaming
How SimpleViewer streams dual and triple 4K monitor setups at 60 FPS with instant display switching, adaptive bitra...