Chapter 7. AutoRAG configuration parameters
The following user-configurable parameters are available when you create an AutoRAG optimization run in the OpenShift AI dashboard. AutoRAG also uses default values for search space parameters that you cannot change.
7.1. User-configurable parameters Copy linkLink copied to clipboard!
You set the following parameters when you create an AutoRAG optimization run.
| Parameter | Description | Values |
|---|---|---|
| Optimization metric | The metric that AutoRAG uses to rank RAG patterns. | Answer faithfulness (default), Answer correctness, Context correctness |
| Maximum RAG patterns | The number of RAG configurations that AutoRAG evaluates. | A value between 4 and 20. Default: 8. |
| Foundation models | The large language models used for answer generation. Discovered from your OGX instance. | All available models are selected by default. Clear the checkbox for models to exclude them. |
| Embedding models | The models used to create vector embeddings and to encode queries during retrieval. Discovered from your OGX instance. | All available models are selected by default. Clear the checkbox for models to exclude them. |
| Vector database | The vector database where AutoRAG stores document embeddings. | A remote Milvus or pgvector (PostgreSQL) instance registered as a vector I/O provider with your OGX instance. |
| Input documents | Documents that AutoRAG processes and indexes for retrieval. | PDF, DOCX, PPTX, Markdown, HTML, TXT. Maximum 32 MiB per file when uploading. Documents in S3 can be selected via the file browser without upload size restrictions. |
| Evaluation dataset | A JSON file with test questions and expected answers for evaluating RAG quality. | JSON format. See Prepare test data for AutoRAG. |
7.2. Search space defaults Copy linkLink copied to clipboard!
AutoRAG explores the following search space during optimization. For parameters with multiple default values, AutoRAG evaluates combinations of those values across RAG configurations. These values are not configurable through the dashboard.
| Parameter | Default values | Description |
|---|---|---|
| Chunking method | Recursive (recursive character text splitting) | The method used to split documents into chunks. |
| Chunk size | 1024, 2048 | The target size of each document chunk in characters. |
| Chunk overlap | 128, 256 | The number of overlapping characters between consecutive chunks. |
| Retrieval method | Simple (direct chunk retrieval) | The method used to retrieve relevant chunks from the vector database. |
| Number of chunks | 3, 5, 10 | The number of document chunks retrieved per query. |
| Search mode | Vector, Hybrid | The search strategy. Hybrid search combines vector and keyword search and is available only with Milvus. |
7.3. Recommended embedding models Copy linkLink copied to clipboard!
For best results, use BAAI/bge-m3 as your embedding model. It supports more than 100 languages, dense and sparse retrieval, and requires approximately 1.1 GB of memory (fp16).
7.4. Recommended foundation models Copy linkLink copied to clipboard!
The following foundation models are recommended for use with AutoRAG, organized by resource tier.
| Tier | Model | Best for |
|---|---|---|
| Lightweight |
| Highest retrieval precision among small models. Suitable for low-latency, high-concurrency workloads on limited GPU resources. |
| Lightweight |
| Text extraction and summarization on edge clusters or single-GPU environments. |
| Medium |
| Strict instruction following, structured JSON output, and tool-call formatting. Suitable for pipelines that require precise output control. |
| Enterprise |
| Cross-document synthesis, multi-step reasoning, and complex tool execution across large datasets. |
- Lightweight
- Limited GPU resources or low-latency, high-concurrency workloads.
- Medium
- Higher answer correctness across multiple documents with moderate infrastructure.
- Enterprise
- Complex reasoning, multi-step tool execution, or large-scale document synthesis.