feat: enhance squid config#30146
Conversation
| Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
There was a problem hiding this comment.
Pull request overview
This PR enhances the Squid proxy configuration to address timeout issues with high-concurrency image requests by adding comprehensive performance optimization settings including connection management, timeout configurations, persistent connections, and caching improvements.
Key Changes:
- Added extensive timeout configurations (connect, request, read) optimized for image handling
- Enabled persistent connections for both server and client sides with connection pooling
- Configured memory caching with 256 MB allocation and DNS optimization with public resolvers
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| # Timeout configurations for image requests | ||
| connect_timeout 30 seconds | ||
| request_timeout 2 minutes | ||
| read_timeout 2 minutes |
There was a problem hiding this comment.
This would make HTTP_REQUEST_MAX_WRITE_TIMEOUT invalid, as it's default value is 600s in /docker/.env
There was a problem hiding this comment.
workflow HTTP node would get "504 Bad Gateway" status code when response time exceed 2 minutes
Important
Fixes #<issue number>.Summary
fix #29642
Performance Optimization Configuration
These configurations should significantly improve timeout issues when handling high-concurrency image requests. You need to restart the squid service for the changes to take effect.
Screenshots
Checklist
dev/reformat(backend) andcd web && npx lint-staged(frontend) to appease the lint gods