mirror of
https://github.com/NoFxAiOS/nofx.git
synced 2026-07-03 02:50:59 +08:00
bb2edfc293
## Problem
Binance WebSocket has a hard limit of 1024 streams per connection.
Without protection:
- 300 coins × 4 timeframes = 1200 streams → Connection REJECTED
- System fails to start with "全市場掃描" mode
## Solution
Implement intelligent auto-downgrade mechanism with transparent logging.
### Changes to market/monitor.go (+42 lines)
**1. Add Constants**:
```go
const (
MaxStreamsPerConnection = 1024 // Binance hard limit
SafeMaxSymbols = 250 // Safe limit (97.7% usage, 2.3% buffer)
)
```
**2. Add Stream Count Check in Initialize()**:
- Calculate total streams: `len(symbols) × len(subKlineTime)`
- If exceeds 250 coins → Auto-downgrade to first 250
- Display detailed adjustment logs
**3. Add Usage Rate Display**:
```
✓ WebSocket 訂閱: X 個幣種 × 4 時間週期 = Y 流 (Z% 用量)
```
**4. Add High Usage Warning (>90%)**:
```
⚠️ 警告: 訂閱流使用率較高 (93.8%)，建議減少幣種數量以確保穩定性
```
## Behavior by Scenario
| Coins | Original Streams | Adjusted Streams | Behavior |
|-------|-----------------|------------------|----------|
| 8 | 32 | 32 | ✅ Normal |
| 100 | 400 | 400 | ✅ Normal |
| 150 | 600 | 600 | ✅ Normal |
| 240 | 960 | 960 | ⚠️ Warning |
| 300 | 1200 | **1000** | 🔄 Auto-downgrade |
| 500 | 2000 | **1000** | 🔄 Auto-downgrade |
## Example Logs
### Normal Case (8 coins):
```
找到 8 个交易对
✓ WebSocket 訂閱: 8 個幣種 × 4 時間週期 = 32 流 (3.1% 用量)
```
### Auto-downgrade Case (300 coins):
```
找到 300 个交易对
⚠️ 幣種數量過多，自動調整:
- 原始數量: 300 個幣種 (1200 流)
- Binance 限制: 1024 流/連接
- 時間週期: 4 ([3m 15m 1h 4h])
- 調整後: 250 個幣種 (1000 流)
- 已過濾: 前 250 個幣種保留，其餘忽略
✓ WebSocket 訂閱: 250 個幣種 × 4 時間週期 = 1000 流 (97.7% 用量)
⚠️ 警告: 訂閱流使用率較高 (97.7%)，建議減少幣種數量以確保穩定性
```
## Benefits
- ✅ System always starts successfully (no crashes)
- ✅ Transparent logging (users know what happened)
- ✅ Safe buffer (2.3% headroom for reconnections)
- ✅ No breaking changes (8-250 coins unchanged)
- ✅ Covers all realistic use cases (AI500 + OI Top = ~150 coins)
## Why 250, not 256?
- 256 × 4 = 1024 (no buffer, risky during reconnections)
- 250 × 4 = 1000 (24 stream buffer = 2.3% safety margin)
- Future-proof for potential 5th timeframe
Related: 15m/1h timeframe addition, WebSocket architecture merge