Performance optimization
Optimal Configuration
Configuring your Feed API consumer with optimal settings ensures maximum throughput and resource efficiency. The following configuration is recommended for production environments:
Batch Size:
- Recommended: 200 records per request
- Range: 100-250 records
- Rationale: This balances throughput with memory usage for most deployment scenarios
Poll Interval:
- When hasNext is true: Immediate (no wait) - fetch the next batch without delay
- When hasNext is false: 5-10 seconds - wait before retrying
- With consecutive empty responses: 10-30 seconds (with exponential backoff) - increase wait time to reduce unnecessary API calls
Connection Pooling:
- Enabled: true
- Pool Size: 5-10 concurrent connections
- Keep-Alive: true
Request Timeouts:
- Connect Timeout: 30 seconds
- Read Timeout: 45 seconds
- Total Timeout: 60 seconds
Throughput Estimates
Feed API performance varies based on your data volume and polling strategy. Here are typical throughput scenarios:
Low Volume Scenario:
- Event Rate: 100-500 events/minute
- Recommended Batch Size: 100 records
- Poll Interval: 5-10 seconds
- Estimated Throughput: All events processed within 1-2 minutes
High Volume Scenario:
- Event Rate: 10,000+ events/minute
- Recommended Batch Size: 250 records (maximum)
- Poll Interval: Immediate when hasNext=true
- Estimated Throughput: Near real-time (less than 5 second lag)
Burst Scenario:
- Event Rate: Variable/bursty traffic
- Strategy: Adaptive polling with exponential backoff
- Benefit: Automatically handles both high and low volume efficiently without manual intervention
Updated about 2 hours ago