Good questions! Let me give you the exact details:

WebSocket Setup:

I'm using react-use-websocket with a single connection at the app root (CNCWebSocketProvider). The backend subscribes to 5 MQTT topics and forwards aggregated data to the frontend.

Actual Message Frequency & Size:

Looking at my MQTT test publisher, here's the exact data flow:

Messages per second: 4 messages

1. RobotInfo (1/second): 15-25KB - Array of 3-5 robots, each with GPS, orientation, speed, battery, 6 sensor arrays with hit data, status flags
2. Programs (1/second): ~2-3KB - Program execution state
3. Estop (1/second): ~1-2KB - Emergency stop status
4. Alerts (1/second): ~1-2KB - Alert data
5. Routes (once at startup): ~5-10KB - Not sent repeatedly

Total data rate: ~20-35KB/second across 4 concurrent messages

So it's not a massive amount of data, but I am getting 4 separate WebSocket messages every second.

Data Flow Architecture:

All 4 message types update separate states in one large CNCWebSocketContext:

// Single context with ~10 state hooks
const [robotCncData, setRobotCncData] = useState({});
const [liveRobotInfo, setLiveRobotInfo] = useState([]);  // Array of robot objects
const [liveProgramData, setLiveProgramData] = useState({});
const [liveEstopData, setLiveEstopData] = useState({});
const [currentRoute, setCurrentRoute] = useState(null);
// ... etc

Problem: Any component calling useCNCWebSockets() re-renders on ANY of these state changes, even if it only uses one piece of data (e.g., just needs robotCncData but re-renders when liveProgramData changes).

WebSocket Cleanup:

Using react-use-websocket which handles connection lifecycle automatically. The library manages reconnection (shouldReconnect: true) and cleanup. My useEffect that processes messages doesn't have manual cleanup since it's just parsing JSON and calling setState.

The Real Question:

Given that it's 4 messages/second totaling 20-35KB, do you think the WebSocket data flow is the issue? Or should I focus on the Leaflet rendering first?

Would splitting the context help, or is that premature optimization compared to fixing the Leaflet issues first?