This repository was archived by the owner on Mar 20, 2026. It is now read-only.
models scores #244
yiftachashkenazi
started this conversation in
Design Discussions
Replies: 1 comment 2 replies
-
|
@Goldziher this is after 5 test all the same. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
RAG Model Performance Report
Test Type: Configurable RAG Quality Benchmark
Benchmark ID: configurable_rag_quality_20250728_132135
Test Timestamp: 2025-07-28T16:21:35.103387
Total Configurations Tested: 3
Total Test Time: 18.37 minutes
Executive Summary
This report details the performance and quality of three different embedding models within a configurable RAG pipeline. The models tested were:
production_minilm_2000,scibert_2000, andmpnet_2000. The benchmark focused on evaluating retrieval relevance, performance metrics, and overall RAG quality.Key Findings:
production_minilm_2000(384d).Model Configurations
production_minilm_2000sentence-transformers/all-MiniLM-L12-v2scibert_2000allenai/scibert_scivocab_uncasedmpnet_2000sentence-transformers/all-mpnet-base-v2Comprehensive Comparison
production_minilm_2000scibert_2000mpnet_2000Detailed Analysis
Performance Analysis
production_minilm_2000is the clear leader, processing significantly more vectors per second.production_minilm_2000also demonstrates the highest search throughput, indicating faster query processing.production_minilm_2000model is by far the most memory-efficient, requiring minimal memory compared to the 768d models, which surprisingly show negative memory usage (this might indicate a reporting anomaly or a specific way memory is calculated in the benchmark).RAG Quality Metrics
mpnet_2000scores the highest in average relevance, suggesting it is better at retrieving semantically similar documents.scibert_2000follows closely, withproduction_minilm_2000scoring lowest in this metric.scibert_2000andmpnet_2000) have considerably longer retrieval times compared toproduction_minilm_2000.scibert_2000retrieved the most documents on average, though the difference is marginal.Advanced Quality Metrics
scibert_2000achieved the highest query quality score, suggesting its generated queries were more effective.production_minilm_2000scored the highest in Query AI Score, implying its generated queries were deemed most effective by the AI evaluator.Key Insights
production_minilm_2000is the superior choice. It offers the best throughput and the lowest memory footprint.mpnet_2000is the best performer, closely followed byscibert_2000. These models, with their larger dimensionality, seem to capture semantic nuances more effectively.production_minilm_2000model's lower relevance scores, despite its performance advantages, suggest that for applications where capturing very specific or nuanced information is critical, exploring larger dimensional models might be beneficial, provided the performance impact is acceptable.Conclusion
The choice of model depends on specific application needs. If speed and resource efficiency are paramount, the existing
production_minilm_2000configuration is robust. However, if achieving the highest possible relevance is the primary goal,mpnet_2000orscibert_2000offer a clear advantage, albeit with a performance penalty. Further testing with different chunking strategies or a broader range of queries could provide additional insights.Beta Was this translation helpful? Give feedback.
All reactions