Custom document loaders in LangChain - Performance & Optimization

Performance: Custom document loaders

MEDIUM IMPACT

Custom document loaders affect page load speed and responsiveness by controlling how and when documents are fetched and processed.

Loading large documents for processing in a web app

LangChain

import asyncio
import aiofiles
class GoodLoader:
    async def load(self):
        # Loads document asynchronously in chunks
        data = ''
        async with aiofiles.open('large_doc.txt', 'r') as f:
            async for line in f:
                data += line
        return data

Loads document asynchronously in chunks, freeing main thread and allowing rendering to proceed.

📈 Performance GainNon-blocking load reduces LCP delay by 50-80%

Loading large documents for processing in a web app

LangChain

class BadLoader:
    def load(self):
        # Loads entire document synchronously
        with open('large_doc.txt', 'r') as f:
            data = f.read()
        return data

Loads entire document synchronously blocking the main thread and delaying rendering.

📉 Performance CostBlocks rendering for 100+ ms depending on document size

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous full document load	Minimal DOM nodes	0 reflows	Blocks paint until load completes	[X] Bad
Asynchronous chunked document load	Minimal DOM nodes	0 reflows	Non-blocking paint, faster LCP	[OK] Good

Rendering Pipeline

Custom document loaders impact the loading and scripting stages by controlling when document data becomes available for rendering and processing.

→Loading

→Scripting

→Rendering

⚠️ BottleneckLoading stage due to synchronous blocking or large data fetches

Core Web Vital Affected

LCP

Custom document loaders affect page load speed and responsiveness by controlling how and when documents are fetched and processed.

Optimization Tips

1Always load documents asynchronously to avoid blocking rendering.

2Process large documents in chunks to keep the main thread free.

3Avoid synchronous file or network reads in custom loaders to improve LCP.

Performance Quiz - 3 Questions

What is the main performance benefit of using asynchronous custom document loaders?

A They prevent blocking the main thread during document loading

B They reduce the number of DOM nodes created

C They increase the size of the JavaScript bundle

D They eliminate the need for CSS styles

DevTools: Performance

How to check: Record a performance profile while loading the document. Look for long tasks blocking the main thread during load.

What to look for: Long blocking tasks indicate synchronous loading; shorter tasks with gaps indicate asynchronous loading improving responsiveness.

Practice

1. What is the main purpose of creating a custom document loader in Langchain?

easy

A. To load and preprocess documents from any data source before use

B. To create user interfaces for document display

C. To train machine learning models directly

D. To manage database connections automatically

Solution

1. Step 1: Understand the role of document loaders

   Document loaders bring data into Langchain, preparing it for processing.

2. Step 2: Identify the purpose of custom loaders

   Custom loaders allow loading from any source and preprocessing like cleaning or adding metadata.

3. Final Answer:

   To load and preprocess documents from any data source before use -> Option A

4. Quick Check:

   Custom loaders = load + preprocess documents [OK]

Hint: Custom loaders bring in and prep data from any source [OK]

Common Mistakes:

• Confusing loaders with UI components
• Thinking loaders train models
• Assuming loaders manage databases

2. Which of the following is the correct way to start defining a custom document loader class in Langchain?

easy

A. class MyLoader():\n def load(self):\n pass

B. def MyLoader():\n return BaseLoader.load()

C. class MyLoader(BaseLoader):\n def load(self):\n pass

D. class MyLoader(BaseLoader):\n def read(self):\n pass

Solution

1. Step 1: Check inheritance from BaseLoader

   Custom loaders must inherit from BaseLoader to fit Langchain's pattern.

2. Step 2: Confirm the method name is load

   The required method to implement is load(), not read().

3. Final Answer:

   class MyLoader(BaseLoader):\n def load(self):\n pass -> Option C

4. Quick Check:

   Inherit BaseLoader + define load() method [OK]

Hint: Inherit BaseLoader and implement load() method [OK]

Common Mistakes:

• Not inheriting from BaseLoader
• Using wrong method name like read()
• Defining function instead of class

3. Given this custom loader code snippet, what will print(docs) output?

from langchain.schema import Document
from langchain.document_loaders.base import BaseLoader

class SimpleLoader(BaseLoader):
    def load(self):
        return [Document(page_content='Hello World', metadata={'source': 'test'})]

loader = SimpleLoader()
docs = loader.load()

medium

A. [Document(page_content='Hello World', metadata={'source': 'test'})]

B. ['Hello World']

C. None

D. SyntaxError

Solution

1. Step 1: Analyze the load method return value

   The load method returns a list with one Document object containing content and metadata.

2. Step 2: Understand what docs holds

   docs is assigned the list returned, so printing docs shows the list with the Document instance.

3. Final Answer:

   [Document(page_content='Hello World', metadata={'source': 'test'})] -> Option A

4. Quick Check:

   load() returns list of Document objects [OK]

Hint: load() returns list of Document objects, not strings [OK]

Common Mistakes:

• Expecting a list of strings instead of Document objects
• Thinking load() returns None
• Assuming syntax error due to imports

4. Identify the error in this custom loader code:

from langchain.document_loaders.base import BaseLoader

class FaultyLoader(BaseLoader):
    def load(self):
        docs = []
        docs.append('Just a string')
        return docs

loader = FaultyLoader()
loader.load()

medium

A. The load method must be named read

B. BaseLoader cannot be inherited directly

C. The class must not have a load method

D. The load method should return Document objects, not strings

Solution

1. Step 1: Check what load returns

   The load method returns a list with a string instead of Document objects.

2. Step 2: Recall Langchain expects Document objects

   Custom loaders must return Document instances, not plain strings, for proper processing.

3. Final Answer:

   The load method should return Document objects, not strings -> Option D

4. Quick Check:

   load() must return Document objects [OK]

Hint: load() must return Document objects, not plain strings [OK]

Common Mistakes:

• Returning strings instead of Document objects
• Misnaming the load method
• Thinking BaseLoader can't be inherited

5. You want to create a custom loader that reads text files from a folder, adds the filename as metadata, and returns Document objects. Which approach correctly implements this?

hard

A. Use BaseLoader directly without subclassing, call load() with folder path argument

B. Inherit BaseLoader, implement load() to read files, create Document with content and metadata filename, return list

C. Create a function that returns file contents as strings without Document wrapping

D. Subclass BaseLoader but return raw file paths as strings in load()

Solution

1. Step 1: Confirm inheritance and method implementation

   Custom loaders must subclass BaseLoader and implement load() method.

2. Step 2: Ensure load reads files and returns Document objects with metadata

   Reading files and wrapping content in Document with filename metadata is correct.

3. Final Answer:

   Inherit BaseLoader, implement load() to read files, create Document with content and metadata filename, return list -> Option B

4. Quick Check:

   Subclass + load() returns Document list with metadata [OK]

Hint: Subclass BaseLoader, load files, wrap in Document with metadata [OK]

Common Mistakes:

• Not subclassing BaseLoader
• Returning strings instead of Document objects
• Ignoring metadata addition