Polling as fallback in Flask - Performance & Optimization

Performance: Polling as fallback

MEDIUM IMPACT

Polling as fallback affects how quickly the page updates with new data and impacts server load and client rendering frequency.

Updating client UI with server data when real-time push is unavailable

Flask

import time
from flask import Flask, jsonify
app = Flask(__name__)

last_value = None

@app.route('/data')
def data():
    global last_value
    current = time.time()
    if last_value is None or current - last_value > 5:
        last_value = current
        return jsonify({'value': current})
    else:
        return jsonify({'value': None})  # No update

Polling less frequently or only sending updates when data changes reduces unnecessary reflows and server load.

📈 Performance GainReduces reflows and server requests by up to 80%, improving interaction responsiveness.

Updating client UI with server data when real-time push is unavailable

Flask

import time
from flask import Flask, jsonify
app = Flask(__name__)

@app.route('/data')
def data():
    # Client polls every 1 second
    return jsonify({'value': time.time()})

Client requests data every second regardless of changes, causing many unnecessary server hits and browser reflows.

📉 Performance CostTriggers frequent reflows and increases server CPU usage; can block rendering if responses are slow.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Frequent polling every 1s	High (many updates)	High (many reflows)	High (many paints)	[X] Bad
Conditional polling every 5s or on change	Low (few updates)	Low (few reflows)	Low (few paints)	[OK] Good

Rendering Pipeline

Polling triggers network requests that cause the browser to recalculate styles and layout if new data changes the DOM. Frequent polling increases Layout and Paint stages.

→Network

→Style Calculation

→Layout

→Paint

⚠️ BottleneckLayout and Paint due to frequent DOM updates from polling responses

Core Web Vital Affected

INP

Polling as fallback affects how quickly the page updates with new data and impacts server load and client rendering frequency.

Optimization Tips

1Avoid polling more often than necessary to reduce reflows and server load.

2Send updates only when data changes to minimize DOM updates.

3Use polling as a fallback only when real-time push is unavailable.

Performance Quiz - 3 Questions

What is the main performance downside of frequent polling as a fallback?

A It reduces the size of the JavaScript bundle.

B It causes many unnecessary reflows and server load.

C It improves Largest Contentful Paint (LCP).

D It eliminates the need for CSS.

DevTools: Performance

How to check: Record a performance profile while the page is polling. Look for frequent Layout and Paint events triggered by network responses.

What to look for: High frequency of Layout and Paint events indicates costly polling; fewer events mean better performance.

Practice

1. What is the main reason to use polling as a fallback in Flask applications?

easy

A. To regularly ask the server for updates when real-time methods fail

B. To reduce the number of server requests to zero

C. To make the server push updates automatically without client requests

D. To avoid any communication between client and server

Solution

1. Step 1: Understand polling purpose

   Polling sends repeated requests to the server to check for updates.

2. Step 2: Identify fallback use

   Polling is used when real-time communication methods like WebSockets are unavailable or fail.

3. Final Answer:

   To regularly ask the server for updates when real-time methods fail -> Option A

4. Quick Check:

   Polling = fallback for updates [OK]

Hint: Polling means repeated requests when real-time fails [OK]

Common Mistakes:

• Thinking polling reduces server requests
• Confusing polling with server push
• Believing polling stops communication

2. Which Flask code snippet correctly implements a simple polling endpoint that returns JSON data?

easy

A. from flask import Flask
app = Flask(__name__)

@app.route('/poll')
def poll():
return {'status': 'ok', 'time': datetime.now()}

B. from flask import Flask
app = Flask(__name__)

@app.route('/poll')
def poll():
return 'status: ok'

C. from flask import Flask, json
app = Flask(__name__)

@app.route('/poll')
def poll():
return json.dumps({'status': 'ok'})

D. from flask import Flask, jsonify
app = Flask(__name__)

@app.route('/poll')
def poll():
return jsonify({'status': 'ok'})

Solution

1. Step 1: Check Flask imports and response format

   Using jsonify is the correct way to return JSON responses in Flask.

2. Step 2: Verify route and function syntax

   from flask import Flask, jsonify app = Flask(__name__) @app.route('/poll') def poll(): return jsonify({'status': 'ok'}) uses @app.route and returns jsonify({'status': 'ok'}) correctly.

3. Final Answer:

   Correct Flask polling endpoint returning JSON with jsonify -> Option D

4. Quick Check:

   jsonify for JSON response = from flask import Flask, jsonify app = Flask(__name__) @app.route('/poll') def poll(): return jsonify({'status': 'ok'}) [OK]

Hint: Use jsonify to return JSON responses in Flask [OK]

Common Mistakes:

• Returning plain string instead of JSON
• Using json.dumps without Response object
• Returning dict directly without jsonify

3. Given this Flask polling endpoint code, what will the client receive when requesting '/poll'?

from flask import Flask, jsonify
app = Flask(__name__)

@app.route('/poll')
def poll():
    data = {'message': 'Hello', 'count': 5}
    return jsonify(data)

medium

A. Hello 5

B. {"message": "Hello", "count": 5}

C. {message: Hello, count: 5}

D. Error: jsonify not defined

Solution

1. Step 1: Understand jsonify output

   jsonify converts Python dict to JSON string with double quotes and correct syntax.

2. Step 2: Check returned data format

   The returned JSON string will be {"message": "Hello", "count": 5} as a JSON response.

3. Final Answer:

   {"message": "Hello", "count": 5} -> Option B

4. Quick Check:

   jsonify returns JSON string = {"message": "Hello", "count": 5} [OK]

Hint: jsonify returns JSON string with double quotes [OK]

Common Mistakes:

• Expecting plain text instead of JSON
• Confusing Python dict syntax with JSON
• Assuming jsonify is undefined

4. Identify the error in this Flask polling endpoint code:

from flask import Flask, jsonify
app = Flask(__name__)

@app.route('/poll')
def poll():
    data = {'status': 'ok'}

medium

A. Function poll() is missing a return statement

B. Missing @app.route decorator

C. Flask app is not created properly

D. Returning a dict directly without using jsonify causes an error

Solution

1. Step 1: Check for return statement

   The poll() function defines data but does not return it.

2. Step 2: Verify function completeness

   Missing return statement means the endpoint returns None by default, causing unexpected empty response.

3. Final Answer:

   Function poll() is missing a return statement -> Option A

4. Quick Check:

   Missing return in view function [OK]

Hint: Always include return statement in Flask route handlers [OK]

Common Mistakes:

• Missing return statement in route function
• Forgetting route decorator
• Not creating Flask app instance

5. You want to implement polling as a fallback in a Flask app that first tries WebSocket for real-time updates. Which approach correctly combines both methods?

hard

A. Use WebSocket and polling simultaneously without fallback logic

B. Only use polling and ignore WebSocket support

C. Use WebSocket for updates; if unsupported, client polls '/poll' endpoint every 5 seconds

D. Use polling only on the server side without client requests

Solution

1. Step 1: Understand fallback strategy

   Fallback means trying WebSocket first, then polling if WebSocket fails or is unsupported.

2. Step 2: Identify correct client-server interaction

   Client tries WebSocket; if it fails, client sends repeated requests to '/poll' endpoint every few seconds.

3. Final Answer:

   Use WebSocket for updates; if unsupported, client polls '/poll' endpoint every 5 seconds -> Option C

4. Quick Check:

   Fallback = WebSocket then polling [OK]

Hint: Try WebSocket first, then poll if needed [OK]

Common Mistakes:

• Ignoring fallback and using only polling
• Using polling without client requests
• Running both methods without fallback logic