[FEATURE] The experiment can support streaming response
- Dominant language
- Go
- Stars
- 5.7k
- Forks
- 795
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 29
Description
### 📋 Please ensure that:
- [x] I have searched existing issues to avoid duplicates
- [x] I have provided a clear problem statement and solution
- [x] I understand this is a feature request and not a bug report
- [x] I am willing to help implement this feature if needed
- [x] I have submitted this feature request in English (otherwise it will not be processed)
### 🎯 Problem Statement
The current experiment only supports non streaming responses. Under large-scale input tokens, non streaming responses are prone to timeout. We hope to support streaming responses
### 💡 Proposed Solution
The current experiment only supports non streaming responses. Under large-scale input tokens, non streaming responses are prone to timeout. We hope to support streaming responses
### 📋 Use Cases
The current experiment only supports non streaming responses. Under large-scale input tokens, non streaming responses are prone to timeout. We hope to support streaming responses
### ⚡ Priority
Critical - Essential for my workflow
### 🔧 Component
None
### 🔄 Alternatives Considered
_No response_
### 🎨 Mockups/Designs
_No response_
### ⚙️ Technical Details
_No response_
### ✅ Acceptance Criteria
_No response_
### 📝 Additional Context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.