Creating tables (db.create_all) in Flask - Performance Optimization Steps

Performance: Creating tables (db.create_all)

MEDIUM IMPACT

This affects the initial page load time and backend response speed when the database tables are created or checked.

Creating database tables in a Flask app

Flask

from flask import Flask
from flask_sqlalchemy import SQLAlchemy

app = Flask(__name__)
app.config['SQLALCHEMY_DATABASE_URI'] = 'sqlite:///test.db'
db = SQLAlchemy(app)

with app.app_context():
    db.create_all()

@app.route('/')
def index():
    return 'Hello World!'

if __name__ == '__main__':
    app.run()

Creating tables once during app startup avoids blocking requests and improves response speed.

📈 Performance GainNo blocking during requests, reducing LCP by 100-300ms on first load.

Creating database tables in a Flask app

Flask

from flask import Flask
from flask_sqlalchemy import SQLAlchemy

app = Flask(__name__)
app.config['SQLALCHEMY_DATABASE_URI'] = 'sqlite:///test.db'
db = SQLAlchemy(app)

@app.route('/')
def index():
    db.create_all()
    return 'Hello World!'

if __name__ == '__main__':
    app.run()

Calling db.create_all inside a route blocks the request until tables are created, causing slow response and poor user experience.

📉 Performance CostBlocks rendering for 100-300ms on first request, increasing LCP and delaying page load.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
db.create_all inside route	N/A (server-side)	N/A	Blocks response, delays paint	[X] Bad
db.create_all at startup	N/A (server-side)	N/A	Non-blocking response, faster paint	[OK] Good

Rendering Pipeline

Table creation happens on the server side before sending the response. If done during a request, it delays the server response, increasing time to first byte and LCP.

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing (blocking db.create_all call)

Core Web Vital Affected

LCP

This affects the initial page load time and backend response speed when the database tables are created or checked.

Optimization Tips

1Run db.create_all once during app startup, not inside request handlers.

2Avoid blocking operations during request processing to improve LCP.

3Use app.app_context() when creating tables outside routes.

Performance Quiz - 3 Questions

What is the main performance issue with calling db.create_all inside a Flask route?

A It blocks the server response, increasing page load time

B It increases client-side rendering time

C It causes excessive DOM reflows

D It increases CSS selector complexity

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and check the time for the first request to the server.

What to look for: Look for long server response time (TTFB) indicating blocking operations like db.create_all during request.