Contextual compression in LangChain - Performance & Optimization

Performance: Contextual compression

MEDIUM IMPACT

Contextual compression affects how much data is sent and processed during language model calls, impacting network load and response time.

Sending large text context to a language model for processing

LangChain

compressed_context = compress_context(get_full_text())
response = llm.call(compressed_context)

Compressing context reduces payload size, lowering network latency and speeding up model response.

📈 Performance Gainreduces request size by 60-80%; cuts response time by 100-300ms

Sending large text context to a language model for processing

LangChain

full_context = get_full_text()
response = llm.call(full_context)

Sending the entire uncompressed context increases data size, causing slower network transfer and longer model processing time.

📉 Performance Costblocks rendering for 200-500ms depending on context size; adds 50-200kb to request payload

Performance Comparison

Pattern	Data Size Sent	Network Latency	Server Processing	Verdict
Uncompressed Context	Large (50-200kb)	High (200-500ms)	Longer	[X] Bad
Compressed Context	Small (10-40kb)	Low (100-200ms)	Shorter	[OK] Good

Rendering Pipeline

Contextual compression reduces the data sent to the language model API, minimizing network transfer and server processing before the response is rendered.

→Network Transfer

→Server Processing

→Rendering

⚠️ BottleneckNetwork Transfer and Server Processing

Core Web Vital Affected

LCP

Contextual compression affects how much data is sent and processed during language model calls, impacting network load and response time.

Optimization Tips

1Always compress large context before sending to language models to reduce payload size.

2Smaller payloads reduce network latency and server processing time, improving LCP.

3Use efficient compression algorithms that balance size reduction and CPU cost.

Performance Quiz - 3 Questions

How does contextual compression improve language model call performance?

A By caching all responses locally to avoid network calls

B By reducing the size of data sent, lowering network and processing time

C By increasing the number of API calls to parallelize requests

D By adding more context to improve accuracy regardless of size

DevTools: Network

How to check: Open DevTools Network tab, send a request with full context, note payload size and timing; then send compressed context request and compare.

What to look for: Look for smaller request payload size and faster response time indicating better compression performance.

Practice

1. What is the main purpose of Contextual compression in langchain?

easy

A. To check grammar and spelling errors

B. To translate text into multiple languages

C. To generate random text from a prompt

D. To reduce text size while keeping its important meaning

Solution

1. Step 1: Understand the goal of contextual compression

   Contextual compression aims to shrink text but keep its main meaning intact.

2. Step 2: Compare options with this goal

   Only To reduce text size while keeping its important meaning matches this goal; others describe different tasks.

3. Final Answer:

   To reduce text size while keeping its important meaning -> Option D

4. Quick Check:

   Contextual compression = reduce text size + keep meaning [OK]

Hint: Focus on meaning retention while reducing text size [OK]

Common Mistakes:

• Confusing compression with translation
• Thinking it generates new text
• Assuming it checks grammar

2. Which of the following is the correct way to create a ContextualCompressionRetriever in langchain?

easy

A. ContextualCompressionRetriever(base_retriever, llm)

B. ContextualCompressionRetriever(llm, base_retriever)

C. ContextualCompressionRetriever()

D. ContextualCompressionRetriever(llm)

Solution

1. Step 1: Recall the constructor parameters order

   The correct order is base_retriever first, then llm.

2. Step 2: Match options with correct order

   Only ContextualCompressionRetriever(base_retriever, llm) matches this order; others have wrong order or missing arguments.

3. Final Answer:

   ContextualCompressionRetriever(base_retriever, llm) -> Option A

4. Quick Check:

   Constructor order = base_retriever, llm [OK]

Hint: Remember: retriever first, then language model [OK]

Common Mistakes:

• Swapping the order of parameters
• Omitting required arguments
• Using empty constructor

3. Given this code snippet, what will be the output type of compressed_docs?

from langchain.retrievers import ContextualCompressionRetriever
compressed_retriever = ContextualCompressionRetriever(base_retriever, llm)
compressed_docs = compressed_retriever.get_relevant_documents(query)

medium

A. A list of compressed Document objects

B. A single compressed string

C. A dictionary with original and compressed texts

D. An error because get_relevant_documents is undefined

Solution

1. Step 1: Understand what get_relevant_documents returns

   It returns a list of Document objects relevant to the query.

2. Step 2: Consider compression effect

   ContextualCompressionRetriever compresses content inside Document objects but still returns a list of Documents.

3. Final Answer:

   A list of compressed Document objects -> Option A

4. Quick Check:

   get_relevant_documents returns list of Documents [OK]

Hint: Retriever methods return lists of Documents, not strings [OK]

Common Mistakes:

• Expecting a single string instead of list
• Thinking it returns a dictionary
• Assuming method does not exist

4. You wrote this code but get an error: TypeError: ContextualCompressionRetriever() missing 1 required positional argument. What is the likely cause?

compressed_retriever = ContextualCompressionRetriever(llm)

medium

A. You passed arguments in the wrong order

B. You forgot to pass the base retriever argument

C. You need to import ContextualCompressionRetriever differently

D. The llm argument is invalid

Solution

1. Step 1: Check constructor requirements

   ContextualCompressionRetriever requires both base_retriever and llm arguments.

2. Step 2: Analyze the error message and code

   The code passes only llm, missing base_retriever, causing the error.

3. Final Answer:

   You forgot to pass the base retriever argument -> Option B

4. Quick Check:

   Missing base retriever causes TypeError [OK]

Hint: Always pass base retriever first, then llm [OK]

Common Mistakes:

• Passing only one argument
• Swapping argument order
• Ignoring error message details

5. You want to speed up document retrieval by compressing context but keep key info. Which approach best applies ContextualCompressionRetriever correctly in a langchain app?

hard

A. Replace your retriever with only an LLM that compresses text manually

B. Use ContextualCompressionRetriever without a base retriever to compress all documents at once

C. Wrap your existing retriever with ContextualCompressionRetriever passing your LLM, then query it

D. Compress documents before adding them to the retriever, then use a normal retriever

Solution

1. Step 1: Understand how ContextualCompressionRetriever works

   It wraps an existing retriever and uses an LLM to compress retrieved documents on the fly.

2. Step 2: Evaluate options for correct usage

   Wrap your existing retriever with ContextualCompressionRetriever passing your LLM, then query it correctly wraps the retriever with compression; others either omit retriever or do manual steps outside the pattern.

3. Final Answer:

   Wrap your existing retriever with ContextualCompressionRetriever passing your LLM, then query it -> Option C

4. Quick Check:

   Wrap retriever + LLM = ContextualCompressionRetriever usage [OK]

Hint: Wrap retriever with compression, don't replace or skip it [OK]

Common Mistakes:

• Skipping base retriever wrapping
• Trying to compress all docs at once without retriever
• Replacing retriever with only LLM