LLMs

R2R uses language models to generate responses based on retrieved context. You can configure R2R’s server-side LLM generation settings with the r2r.toml:

1
[completion]
2
provider = "litellm"
3
concurrent_request_limit = 16
4
5
    [completion.generation_config]
6
    model = "openai/gpt-4o"
7
    temperature = 0.1
8
    top_p = 1
9
    max_tokens_to_sample = 1_024
10
    stream = false
11
    add_generation_kwargs = {}

Key generation configuration options:

• provider: The LLM provider (defaults to “LiteLLM” for maximum flexibility).
• concurrent_request_limit: Maximum number of concurrent LLM requests.
• model: The language model to use for generation.
• temperature: Controls the randomness of the output (0.0 to 1.0).
• top_p: Nucleus sampling parameter (0.0 to 1.0).
• max_tokens_to_sample: Maximum number of tokens to generate.
• stream: Enable/disable streaming of generated text.
• api_base: The base URL for remote communication, e.g. https://api.openai.com/v1

Serving select LLM providers

1
export OPENAI_API_KEY=your_openai_key
2
# .. set other environment variables
3
4
# Optional - Update default model
5
# Set '"model": "openai/gpt-4o-mini"' in `r2r.toml`
6
# then call `r2r serve --config-path=r2r.toml`
7
r2r serve

Runtime Configuration of LLM Provider

R2R supports runtime configuration of the LLM provider, allowing you to dynamically change the model or provider for each request. This flexibility enables you to use different models or providers based on specific requirements or use cases.

Combining Search and Generation

When performing a RAG query, you can dynamically set the LLM generation settings:

1
response = client.rag(
2
    "What are the latest advancements in quantum computing?",
3
    rag_generation_config={
4
        "stream": False,
5
        "model": "openai/gpt-4o-mini",
6
        "temperature": 0.7,
7
        "max_tokens": 150
8
    }
9
)

For more detailed information on configuring other search and RAG settings, please refer to the RAG Configuration documentation.

Next Steps

For more detailed information on configuring specific components of R2R, please refer to the following pages:

• Postgres Configuration
• RAG Configuration
• Ingestion Configuration
• Knowledge Graph Configuration
• Retrieval Configuration