Lazy loading vs eager loading in Flask - Performance Comparison

Performance: Lazy loading vs eager loading

MEDIUM IMPACT

This concept affects how quickly data is fetched and rendered on the page, impacting initial load time and responsiveness.

Fetching related database records in a Flask app using SQLAlchemy

Flask

from sqlalchemy.orm import joinedload
posts = Post.query.options(joinedload(Post.author)).all()
for post in posts:
    print(post.author.name)

This loads posts and their authors in a single query, reducing database calls and speeding up rendering.

📈 Performance Gainsingle database query regardless of number of posts, reducing load time significantly

Fetching related database records in a Flask app using SQLAlchemy

Flask

posts = Post.query.all()
for post in posts:
    print(post.author.name)

This triggers a separate database query for each post's author (N+1 query problem), slowing down page load.

📉 Performance Costtriggers N+1 database queries, increasing load time linearly with number of posts

Performance Comparison

Pattern	Database Queries	Initial Load Time	Network Overhead	Verdict
Lazy Loading	Multiple (N+1 queries)	Lower if few accessed	Lower initially, higher if accessed later	[!] OK
Eager Loading	Single batched query	Higher upfront	Higher upfront, lower later	[OK] Good

Rendering Pipeline

Lazy loading delays fetching related data until it is accessed, reducing initial data processing. Eager loading fetches all related data upfront, increasing initial processing but reducing later delays.

→Data Fetching

→Template Rendering

→Network Requests

⚠️ BottleneckData Fetching stage due to multiple database queries in lazy loading

Core Web Vital Affected

LCP

This concept affects how quickly data is fetched and rendered on the page, impacting initial load time and responsiveness.

Optimization Tips

1Avoid lazy loading if it causes many database queries on page load.

2Use eager loading to fetch related data in one query for faster initial rendering.

3Balance eager and lazy loading based on data size and user interaction patterns.

Performance Quiz - 3 Questions

What is the main performance problem with lazy loading in database queries?

A It loads all data upfront causing slow start

B It blocks rendering completely

C It causes many small queries increasing load time

D It increases bundle size

DevTools: Network

How to check: Open DevTools > Network tab, reload page, and observe number of database API calls or data fetch requests.

What to look for: Multiple small requests indicate lazy loading with many queries; a single larger request indicates eager loading.

Practice

1. What is the main difference between lazy loading and eager loading in Flask ORM?

easy

A. Lazy loading is faster than eager loading in all cases.

B. Lazy loading loads all data at once; eager loading loads data in parts.

C. Lazy loading delays loading related data until accessed; eager loading loads it immediately.

D. Eager loading delays loading related data until accessed; lazy loading loads it immediately.

Solution

1. Step 1: Understand lazy loading behavior

   Lazy loading means related data is not loaded until you specifically ask for it, saving resources initially.

2. Step 2: Understand eager loading behavior

   Eager loading means related data is loaded immediately with the main query, reducing the number of queries later.

3. Final Answer:

   Lazy loading delays loading related data until accessed; eager loading loads it immediately. -> Option C

4. Quick Check:

   Lazy vs eager loading = delay vs immediate load [OK]

Hint: Lazy waits, eager loads now. Remember delay vs immediate [OK]

Common Mistakes:

• Confusing which one loads data immediately
• Thinking lazy loading loads all data at once
• Assuming eager loading is always slower

2. Which of the following is the correct syntax to use eager loading with SQLAlchemy in Flask?

easy

A. query.load_later(Model.related)

B. query.lazyload(Model.related)

C. query.eager(Model.related)

D. query.options(joinedload(Model.related))

Solution

1. Step 1: Identify eager loading syntax in SQLAlchemy

   SQLAlchemy uses joinedload() inside options() to eagerly load related data.

2. Step 2: Check other options for correctness

   lazyload is for lazy loading, eager and load_later are not valid methods.

3. Final Answer:

   query.options(joinedload(Model.related)) -> Option D

4. Quick Check:

   Eager loading = options(joinedload()) [OK]

Hint: Eager loading uses options(joinedload()) in SQLAlchemy [OK]

Common Mistakes:

• Using lazyload instead of joinedload for eager loading
• Trying non-existent methods like eager()
• Confusing method names for loading strategies

3. Given the code below, what will be the output when accessing user.posts if lazy='select' is used?

user = session.query(User).first()
print(user.posts)

medium

A. A list of posts is loaded only when user.posts is accessed.

B. All posts are loaded immediately with the user query.

C. An error occurs because posts are not loaded.

D. Posts are never loaded even when accessed.

Solution

1. Step 1: Understand lazy='select' behavior

   Lazy loading with 'select' means related posts are loaded only when accessed, not with the initial query.

2. Step 2: Analyze code behavior

   When user.posts is printed, a separate query fetches posts at that moment.

3. Final Answer:

   A list of posts is loaded only when user.posts is accessed. -> Option A

4. Quick Check:

   lazy='select' = load on access [OK]

Hint: Lazy='select' loads related data only when accessed [OK]

Common Mistakes:

• Assuming posts load with user query
• Expecting error due to missing posts
• Thinking posts never load

4. Identify the error in this Flask SQLAlchemy code snippet using eager loading:

user = session.query(User).options(lazyload(User.posts)).first()
print(user.posts)

medium

A. Calling print before loading posts.

B. Using lazyload instead of joinedload for eager loading.

C. Incorrect model name used in query.

D. Missing filter() before first().

Solution

1. Step 1: Check loading option used

   The code uses lazyload, which triggers lazy loading, not eager loading.

2. Step 2: Identify correct eager loading method

   For eager loading, joinedload should be used inside options().

3. Final Answer:

   Using lazyload instead of joinedload for eager loading. -> Option B

4. Quick Check:

   Eager loading requires joinedload, not lazyload [OK]

Hint: Eager loading needs joinedload, not lazyload [OK]

Common Mistakes:

• Confusing lazyload and joinedload
• Thinking lazyload triggers eager loading
• Ignoring loading strategy in options()

5. You have a Flask app with a User model and a related Post model. You want to display all users with their posts efficiently. Which approach best balances performance and resource use?

hard

A. Use eager loading with joinedload to load users and posts in one query.

B. Use lazy loading and access posts inside a loop, causing many queries.

C. Load posts separately after loading all users, doubling queries.

D. Avoid loading posts to save resources, showing empty post lists.

Solution

1. Step 1: Consider performance needs

   Loading users and posts in one query reduces database hits and improves speed.

2. Step 2: Compare loading strategies

   Lazy loading inside a loop causes many queries (N+1 problem), and loading posts separately doubles queries.

3. Step 3: Evaluate resource use

   Eager loading with joinedload balances resource use and query count efficiently.

4. Final Answer:

   Use eager loading with joinedload to load users and posts in one query. -> Option A

5. Quick Check:

   Eager loading with joinedload = efficient queries [OK]

Hint: Eager loading with joinedload avoids many queries [OK]

Common Mistakes:

• Using lazy loading causing many queries
• Loading posts separately doubling queries
• Skipping posts causing empty data