[Feature Request]: Revise Default Configuration for High Availability: Current Settings Are Not Production-Ready #9963
Description
Self Checks
- I have searched for existing issues search for existing issues, including closed ones.
- I confirm that I am using English to submit this report (Language Policy).
- Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
- Please do not modify this template :) and fill in all the required fields.
Is your feature request related to a problem?
Describe the feature you'd like
Hi ragflow team,
We're building a production-grade internal AI assistant using ragflow, and during our high-availability (HA) and load testing, we noticed that the default configuration values are too conservative for real-world, scalable deployments.
The current defaults appear optimized for local development or single-instance deployment, but they can become bottlenecks in clustered or high-traffic environments. For example:
🎯 Why This Matters:
These changes would help ragflow transition from a great prototyping tool to a truly production-ready platform. Right now, users must manually discover and tune these settings — often only after hitting performance issues.
By adjusting defaults and providing clear guidance, you’ll empower teams to deploy reliable, scalable AI applications out of the box.
Thanks for considering this enhancement!
Describe implementation you've considered
No response
Documentation, adoption, use case
Additional information
No response