Back to Dispatches
Technical 5 min Apr 18, 2026
YG
Yash Ghodele
Why We Obsess Over 14ms Latency (And Why You Should Too)

Why We Obsess Over 14ms Latency (And Why You Should Too)

Understanding the invisible threshold of human perception and why real-time systems need to be genuinely real-time.

Most software companies talk about features. We talk about milliseconds.

Because in industrial environments, the difference between a system responding in 14 milliseconds and 500 milliseconds isn't merely performance—it's the difference between acting on a problem and discovering it after the damage is already done.

The Human Side of Latency

Humans perceive delays in roughly three categories:

< 100ms

Feels instantaneous. Responds before conscious delay; perceived as physical causation.

100–300ms

Feels responsive, but noticeable to trained eyes. Slight cognitive pause.

> 500ms

Feels noticeably delayed. Lag breaks real-time safety and operator situational awareness.

For a social media app, an extra half-second is annoying. For a factory floor, it can be expensive.

When Milliseconds Become Physical Distance

Consider a spindle rotating at 1000 RPM.

A traditional cloud-based monitoring system with a 500ms delay means the machine completes more than eight full rotations before the operator even sees the alert.

Physics moves first. Software catches up later. Our goal is to make that gap as small as possible.

Why Edge Processing Matters

Typical Cloud Path (200–800ms):

Sensor → 4G Network → API → Database → WebSocket → Browser

Ugam Edge Processing Path (~14ms):

Sensor → ESP32 Edge Decision → MQTT → WebSocket → Dashboard DOM Update

What 14ms Actually Means

The number isn't theoretical. It's measured end-to-end on a stable local factory network:

Component LayerMeasured Latency
Edge Detection (ESP32 On-Chip)2ms
Local MQTT Publish4ms
WebSocket Delivery6ms
React Dashboard DOM State Update2ms
Total End-to-End Latency14ms (1 Frame @ 60 FPS)

The Engineering Philosophy

We don't chase low latency because it looks impressive in benchmarks. We chase it because every millisecond removed from the system reduces the gap between reality and information.

“The real world shouldn't have to wait for software.”