WebSocket events handling in Flask - Performance & Optimization

Performance: WebSocket events handling

MEDIUM IMPACT

This affects the responsiveness and smoothness of real-time updates on the page by controlling how WebSocket events are processed and rendered.

Handling frequent WebSocket messages to update UI

Flask

from flask_socketio import SocketIO, emit
import threading

socketio = SocketIO(app)

def background_task(data):
    result = complex_calculation(data)
    socketio.emit('response', result)

@socketio.on('message')
def handle_message(data):
    threading.Thread(target=background_task, args=(data,)).start()

Offloads heavy processing to a background thread, keeping the main thread free to handle UI and other events.

📈 Performance GainNon-blocking event handling improves responsiveness and reduces input delay

Handling frequent WebSocket messages to update UI

Flask

from flask_socketio import SocketIO, emit

socketio = SocketIO(app)

@socketio.on('message')
def handle_message(data):
    # Heavy processing on main thread
    result = complex_calculation(data)
    emit('response', result)

Heavy processing inside the event handler blocks the main thread, causing UI lag and delayed responses.

📉 Performance CostBlocks main thread during processing, causing input delay and poor INP

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Blocking heavy processing in event handler	Multiple DOM updates per event	Multiple reflows if DOM updated repeatedly	High paint cost due to frequent layout changes	[X] Bad
Background thread processing with batched DOM updates	Batched DOM updates	Single reflow per batch	Lower paint cost due to fewer layout changes	[OK] Good

Rendering Pipeline

WebSocket events trigger JavaScript handlers that update the DOM. If event processing is slow or blocking, it delays Style Calculation, Layout, and Paint stages, hurting responsiveness.

→JavaScript Execution

→Style Calculation

→Layout

→Paint

⚠️ BottleneckJavaScript Execution blocking main thread

Core Web Vital Affected

INP

This affects the responsiveness and smoothness of real-time updates on the page by controlling how WebSocket events are processed and rendered.

Optimization Tips

1Avoid heavy synchronous processing in WebSocket event handlers.

2Use background threads or async tasks for expensive computations.

3Batch DOM updates triggered by WebSocket events to minimize reflows.

Performance Quiz - 3 Questions

What is the main performance issue when handling WebSocket events with heavy processing directly in the event handler?

A It increases network latency

B It blocks the main thread causing input delay

C It reduces the number of WebSocket connections

D It causes memory leaks

DevTools: Performance

How to check: Record a session while WebSocket events occur, then analyze the Main thread activity for long tasks or blocking scripts.

What to look for: Look for long JavaScript execution blocks during event handling that delay input responsiveness.